From: Rajesh Kumar Mallah <mallah.rajesh@gmail.com>
To: arnaulist@andromeiberica.com
Cc: pgsql-admin@postgresql.org
Subject: Re: Suggestions needed about how to dump/restore a database
Date: Tue, 19 Dec 2006 23:11:49 +0530
Message-ID: <a97c77030612190941u463e36a2r5bc055c5ce300c31@mail.gmail.com> (raw)
In-Reply-To: <458821B9.80303@andromeiberica.com>
References: <45881D1A.6090904@andromeiberica.com>
<Pine.LNX.4.64.0612190917130.4926@glacier.frostconsultingllc.com>
<458821B9.80303@andromeiberica.com>
On 12/19/06, Arnau <arnaulist@andromeiberica.com> wrote:
> Hi Jeff,
>
> > On Tue, 19 Dec 2006, Arnau wrote:
> >
> >> I've got a DB in production that is bigger than 2GB that dumping it
> >> takes more than 12 hours.
thats strange , we dump +20GB data in 2 hrs or so.
I have a new server to replace this old one
> >> where I have restore the DB's dump. The problem is I can't afford to
> >> have the server out of business for so long,
if the two biggest tables are *not critical* for application
availability i can dump out their data separately
into two SQL files and later restore it.
once you dump out the data you can drop the tables
from the production DB before dumping out and see
how long it takes.
pg_dump -t schema.table -h hostname -U user <dbname>
can dump out a specific schema.table.
(the exact options are version dependent, which version btw u using?)
it is always desired to know the root cause of why pg_dump is
taking so long in your machine , but in worst case you could take the
approach you suggested.
so I need your advice about
> >> how you'd do this dump/restore. The big amount of data is placed in two
> >> tables (statistics data), so I was thinking in dump/restore all except
> >> this two tables and once the server is running again I'd dump/restore
> >> this data. The problem is I don't know how exactly do this.
> >
> > Arnau,
> >
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: mallah.rajesh@gmail.com, arnaulist@andromeiberica.com
Subject: Re: Suggestions needed about how to dump/restore a database
In-Reply-To: <a97c77030612190941u463e36a2r5bc055c5ce300c31@mail.gmail.com>
References: <45881D1A.6090904@andromeiberica.com> <Pine.LNX.4.64.0612190917130.4926@glacier.frostconsultingllc.com> <458821B9.80303@andromeiberica.com> <a97c77030612190941u463e36a2r5bc055c5ce300c31@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox