{2021-02-12 20:57:57.000953+01 .. 2021-02-12 21:02:10.245561+01}
On Fri, Feb 12, 2021 at 6:38 PM Noah Bergbauer wrote:
> I'm experimenting with that right now. Setting storage to MAIN appears to
> be counterproductive, whereas EXTERNAL with toast_tuple_target = 128 is
> definitely
I'm experimenting with that right now. Setting storage to MAIN appears to
be counterproductive, whereas EXTERNAL with toast_tuple_target = 128 is
definitely an improvement. In theory, this configuration might eliminate
the problem, but due to the toast_tuple_target bug (
https://www.postgresql.org/
This is on version 12.5. The usage pattern is inserts only, no updates or
deletes at all. Hence, fillfactor is set to 100.
It just seems extremely unfortunate in this particular case that Postgres
goes to all the trouble of tetris-ing new tuples into existing pages, only
to cripple performance in
tuples are going to be
quite large (i.e. > 1kB)? Is there any benefit in having postgresql
compress the data when ZFS runs compression regardless?
Thank you,
Noah Bergbauer
