Search Postgresql Archives

Re: database is bigger after dump/restore - why? (60 GB to 109 GB)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Monday, March 07, 2011 2:45:00 pm Aleksey Tsalolikhin wrote:

> 
> Experiment 1:
> hypothesis: something about how large my table has grown is causing
> the TOAST compression to fail on COPY.
> test: pg_dump the big table, cut the dump file in half using
> "/bin/split", add "\." at the end of the file, and load the top half.
> result: database is 50 GB in size.  hypothesis proven false.
> 
> Experiment 2:
> hypothesis: something about Slony is causing the TOAST compression to
> be disabled on COPY.
> test: load the 50% dump file from experiment 1 above into our Stage
> database, which was never touched by Slony.
> result: database is 50 GB in size.  hypothesis proven false.

Hmmm. Another perfectly good line of reasoning shot down. No further thoughts at 
this time. May have to sit down with Jack Daniels and have a talk and see if 
anything shakes loose:)

> 
> 
> Best,
> Aleksey

-- 
Adrian Klaver
adrian.klaver@xxxxxxxxx

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux