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

Re: [NOVICE] systable_getnext_ordered

From: yamt(at)mwd(dot)biglobe(dot)ne(dot)jp (YAMAMOTO Takashi)
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: pgsql-novice(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [NOVICE] systable_getnext_ordered
Date: 2011-02-01 08:35:02
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-novice

thanks for taking a look.

> yamt(at)mwd(dot)biglobe(dot)ne(dot)jp (YAMAMOTO Takashi) writes:
>> the attached patch is to avoid unnecessary detoast'ing and EOF marker pages
>> when possible.  does it make sense?
> The blob page size is already chosen not to allow for out-of-line
> storage, not to mention that pg_largeobject doesn't have a TOAST table.
> So I think avoiding detoasting is largely a waste of time.

doesn't detoasting involve decompression?

> I'm
> unexcited about the other consideration too --- it looks to me like it
> just makes truncation slower, more complicated, and hence more
> bug-prone, in return for a possible speedup that probably nobody will
> ever notice.

slower?  it depends, i guess.

my primary motivation of that part of the patch was to save some space for
certain workloads.  (besides that, leaving unnecessary rows isn't neat,
but it might be a matter of taste.)


> 			regards, tom lane
> -- 
> Sent via pgsql-novice mailing list (pgsql-novice(at)postgresql(dot)org)
> To make changes to your subscription:

In response to

pgsql-novice by date

Next:From: Christian BrennsteinerDate: 2011-02-01 08:50:06
Subject: Re: handling concurrency right why am i wrong?
Previous:From: AmishDate: 2011-02-01 07:03:39
Subject: ERROR: invalid datatype 'FILE'

pgsql-hackers by date

Next:From: Dave PageDate: 2011-02-01 08:47:58
Subject: Re: setlocale and gettext in Postgres
Previous:From: Magnus HaganderDate: 2011-02-01 08:29:34
Subject: Re: setlocale and gettext in Postgres

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