Re: On-disk size of db increased after restore

From: Thom Brown <thom(at)linux(dot)com>
To: Devrim GÜNDÜZ <devrim(at)gunduz(dot)org>
Cc: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, PostgreSQL - General ML <pgsql-general(at)postgresql(dot)org>
Subject: Re: On-disk size of db increased after restore
Date: 2010-09-01 13:17:59
Message-ID: AANLkTimneO7e3SVbPjvrvRzfp1jH5=XcMacvWHJ5W9TF@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2010/9/1 Devrim GÜNDÜZ <devrim(at)gunduz(dot)org>:
> On Tue, 2010-08-31 at 18:08 -0600, Scott Marlowe wrote:
>> ny chance you've restored to different dbs
>> and have two copies?  Or double the data in one db?
>
> Nope. This is a single database, and I restored only once.. # of rows in
> tables match to the ones in prod...

Have you run this on each server?

SELECT datname, pg_database_size(datname)
FROM pg_catalog.pg_database
ORDER BY 2 DESC

And if a single database size differs, run this against the database:

SELECT tablename, pg_table_size(schemaname || '.' || tablename)
FROM pg_catalog.pg_tables
ORDER BY 2 DESC

Should at least narrow down where the space is being used.

--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Igor Neyman 2010-09-01 14:13:49 Re: Table update problem works on MySQL but not Postgres
Previous Message Devrim GÜNDÜZ 2010-09-01 13:02:47 Re: On-disk size of db increased after restore