pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Postgres hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: performance issue in remove_from_unowned_list()
Date: Wed, 13 Mar 2019 14:47:26 +0100
Message-ID: <319fd982-2d28-5879-a8bb-75d1067e8980@2ndquadrant.com> (raw)
In-Reply-To: <CA+TgmobHscKHVBLfZ0k43hXoq6vP8R5CB6i686jCZQtW7ASoaw@mail.gmail.com>
References: <20190310200923.GA4108@alvherre.pgsql>
	<7c599eff-8125-091c-61ef-90e02aa57486@2ndquadrant.com>
	<CA+TgmobHscKHVBLfZ0k43hXoq6vP8R5CB6i686jCZQtW7ASoaw@mail.gmail.com>

On 3/13/19 1:12 PM, Robert Haas wrote:
> On Tue, Mar 12, 2019 at 6:54 PM Tomas Vondra
> <tomas.vondra@2ndquadrant.com> wrote:
>> Attached is a patch adopting the dlist approach - it seems to be working
>> quite fine, and is a bit cleaner than just slapping another pointer into
>> the SMgrRelationData struct. So I'd say this is the way to go.
> 
> What about using a data structure that supports O(1) lookups for any element?
> 
> The current efforts all seem to revolve around correctly guessing from
> which end of the list we are likely to delete stuff, but your research
> suggests that we don't always make such guesses particularly well.
> And it seems unnecessary.
> 

Isn't the the doubly-linked list is doing exactly that?

AFAICS we already maintain a hash table of the smgr relations, and we
look them up in this table. We don't need to look them up in the list of
unowned relations - the whole problem is that with the current
single-linked list, we need to iterate the list anyway to update pointer
in the preceding entry.

regards

-- 
Tomas Vondra                  http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services




view thread (15+ messages)  latest in thread

Message-ID: <319fd982-2d28-5879-a8bb-75d1067e8980@2ndquadrant.com>
Permalink:  ../319fd982-2d28-5879-a8bb-75d1067e8980@2ndquadrant.com/
Also on:    postgresql.org/message-id/319fd982-2d28-5879-a8bb-75d1067e8980@2ndquadrant.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tomas.vondra@2ndquadrant.com, robertmhaas@gmail.com, alvherre@2ndquadrant.com, pgsql-hackers@lists.postgresql.org
  Subject: Re: performance issue in remove_from_unowned_list()
  In-Reply-To: <319fd982-2d28-5879-a8bb-75d1067e8980@2ndquadrant.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox