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]

 



Hi.  Thanks for your replies.

How do I check the fillfactor on the table, please?

(http://www.postgresql.org/docs/8.4/static/sql-createtable.html tells me how
to set it, but I haven't found yet how to read it.)

Same CPU, same filesystem, same blocksize - identical systems.  Same model
of server.  We made them identical on purpose.

The way I check table size including TOAST and Indexes is:

SELECT relname as "Table",
pg_size_pretty(pg_total_relation_size(relid)) As "Size" from
pg_catalog.pg_statio_user_tables ORDER BY
pg_total_relation_size(relid) DESC;

My largest table is 50 GB in size; when I pg_dump it, and then
pg_restore it, it becomes 100 GB in size.

How do I pg_restore it so that it is 50 GB in size?  Is it a setting
to pg_dump or to pg_restore?

Aleksey

-- 
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