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

Re: Modifying TOAST thresholds

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Chris Browne <cbbrowne(at)acm(dot)org>, Jan Wieck <JanWieck(at)Yahoo(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Modifying TOAST thresholds
Date: 2007-04-03 04:26:41
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
I wrote:
> ... should we revel
> in configurability, and allow CREATE TABLE/ALTER TABLE behavior to vary
> depending on the current threshold setting?  We'd have to fix the
> toaster routines to not try to push stuff out-of-line when there is no
> out-of-line to push to ... but I think we probably had better do that
> anyway for robustness, if we're allowing any variability at all in these
> numbers.

Actually, upon looking closely at the toast code, it already does the
right thing when there's no toast table.  Good on someone for getting
that right.  But we still need to think about whether it's sane for
CREATE/ALTER TABLE to condition the create-a-toast-table decision on
a parameter that may now be changeable.

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Luke LonerganDate: 2007-04-03 04:38:52
Subject: Re: Synchronized Scan benchmark results
Previous:From: Tom LaneDate: 2007-04-03 04:21:16
Subject: Re: Modifying TOAST thresholds

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