Re: Modifying TOAST thresholds

From: "Luke Lonergan" <llonergan(at)greenplum(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Chris Browne" <cbbrowne(at)acm(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Modifying TOAST thresholds
Date: 2007-04-03 14:28:31
Message-ID: C237B29F.2B5CE%llonergan@greenplum.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom,

On 4/3/07 7:15 AM, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> BTW, it strikes me that a GUC variable is quite the wrong way to go
> about this. The right way is a table storage parameter, a la FILLFACTOR,
> so that it can be set on a per-table basis. That would also give us a
> chance to fix my concern about needs_toast_table: the case where we
> might need a toast table that we didn't need before is where the toast
> threshold is lowered via ALTER TABLE SET, and we could reasonably make
> that command recheck the situation.

This also seems to also support further development along the vertical
partitioning path. Any thought on support of per-column TOAST tables?

- Luke

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Martijn van Oosterhout 2007-04-03 14:36:18 Re: Bug in UTF8-Validation Code?
Previous Message Bruce Momjian 2007-04-03 14:20:44 Re: [HACKERS] Arrays of Complex Types