Skip site navigation (1) Skip section navigation (2)

Re: unlogged tables vs. GIST

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>,Jeevan Chalke <jeevan(dot)chalke(at)enterprisedb(dot)com>,pgsql-hackers(at)postgresql(dot)org
Subject: Re: unlogged tables vs. GIST
Date: 2013-01-15 19:07:37
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On 2013-01-15 20:58:00 +0200, Heikki Linnakangas wrote:
> On 15.01.2013 20:48, Tom Lane wrote:
> >Robert Haas<robertmhaas(at)gmail(dot)com>  writes:
> >>On Tue, Jan 15, 2013 at 1:10 PM, Heikki Linnakangas
> >><hlinnakangas(at)vmware(dot)com>  wrote:
> >>>Could we stash the counter e.g. in the root page of the index?
> >
> >>That would require maintaining a counter per table rather than a
> >>single global counter, which would be bad because then we'd need to
> >>store one counter in shared memory for every table, rather than just
> >>one, period, which runs up against the fixed sizing of shared memory.
> >
> >I think what Heikki had in mind was that the copy in the index would be
> >the authoritative one, not some image in shared memory.  This'd imply
> >dirtying the root page on every insert, as well as increased contention
> >for the root page, so it might have performance problems.
> Not every insert, just every split. Which might still be a performance
> problem, but an order of magnitude smaller.

I might be dense here and I don't really know that code, but if its only
splits why not do an XLogInsert(XLOG_GIST_NSN) or something there?
Inventing some other form of logging just because its an unlogged table
seems like reinventing the wheel.


Andres Freund

 Andres Freund	         
 PostgreSQL Development, 24x7 Support, Training & Services

In response to

pgsql-hackers by date

Next:From: Sergey KoposovDate: 2013-01-15 19:09:27
Subject: Re: Curious buildfarm failures (fwd)
Previous:From: David FetterDate: 2013-01-15 19:04:24
Subject: Re: json api WIP patch

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group