Re: BUG #16803: create a table only one text/varchar column, storage options toast_tuple_target doesn't work

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: mailtch(at)163(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16803: create a table only one text/varchar column, storage options toast_tuple_target doesn't work
Date: 2021-01-04 18:15:53
Message-ID: 3161684.1609784153@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> create a table only one text/varchar colume, storage options
> toast_tuple_target doesn't work, see:

The reason your first example isn't doing anything is that the tuples are
shorter than TOAST_TUPLE_THRESHOLD, which is the threshold row length for
applying the toasting code at all. The reloption doesn't affect that;
it only changes the target length once we've gotten into the toaster.

It's not real clear to me why whoever provided a knob for
TOAST_TUPLE_TARGET didn't see fit to also provide one for
TOAST_TUPLE_THRESHOLD, but I suppose that was a deliberate choice.
The documentation is certainly clear enough that you can only
adjust the target.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Pavel Stehule 2021-01-04 19:21:07 Re: BUG #16804: substring() function returns "negative substring length" error when using a large length argument
Previous Message Alexander Lakhin 2021-01-04 18:00:00 Re: BUG #16774: PostgreSQL clean build MINGW64 gcc but initdb fails, cannot find startadress CreateProcessAsUserA