From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: Lewis Kapell <lkapell@setonhome.org>
Cc: pgsql-admin@postgresql.org
Subject: Re: TOAST behavior in 8.3 and 8.4
Date: Tue, 13 Apr 2010 14:37:29 -0500
Message-ID: <4BC481A902000025000307F9@gw.wicourts.gov> (raw)
In-Reply-To: <4BC4C592.7020400@setonhome.org>
References: <4BC4BBD4.40706@setonhome.org>
<4BC4798502000025000307F4@gw.wicourts.gov>
<4BC4C592.7020400@setonhome.org>
Lewis Kapell <lkapell@setonhome.org> wrote:
> In tuptoaster.h, just above the declaration of
> TOAST_TUPLES_PER_PAGE, there is a comment which begins: "while
> these can be modified without initdb..."
>
> Does this mean that if I reduce the value of TOAST_TUPLE_THRESHOLD
> and rebuild, I can use an existing database cluster without having
> to run initdb again?
Yes, but it's *possible* that some table which would now seem to
qualify for a toast table, based on the new threshold, would not yet
have one. That would be benign; it just wouldn't be able to toast
values for that table unless you recreated it. You can check
pg_class to find out which tables currently have toast tables.
-Kevin
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: Kevin.Grittner@wicourts.gov, lkapell@setonhome.org
Subject: Re: TOAST behavior in 8.3 and 8.4
In-Reply-To: <4BC481A902000025000307F9@gw.wicourts.gov>
References: <4BC4BBD4.40706@setonhome.org> <4BC4798502000025000307F4@gw.wicourts.gov> <4BC4C592.7020400@setonhome.org> <4BC481A902000025000307F9@gw.wicourts.gov>
* 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