On Fri, Jan 2, 2009 at 11:44, Tom Lane <t...@sss.pgh.pa.us> wrote: > "Robert Haas" <robertmh...@gmail.com> writes: >> I've seen gzip approach 10X on what was basically a large >> tab-separated values file, but I agree that some more experimentation >> to determine the real cause of the problem would be useful. > > If I'm counting on my fingers correctly, you'd need to assume about > 23X compression to get the reported size change... > > An easy way to prove or disprove the point would be to go into > src/backend/utils/adt/pg_lzcompress.c, and change the second entry > in strategy_default_data from "1024 * 1024" to "INT_MAX", then > re-load the table with the modified backend (or you could even > just do "CREATE TABLE foo AS SELECT * FROM existing_table" and > then compare sizes). If that puts the toast table size back where > it had been, then Alex correctly diagnosed the cause.
And the toast file size is *drum roll* 167M. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
