Re: Using RSYNC for replication?

From: Vivek Khera <khera(at)kcilink(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Using RSYNC for replication?
Date: 2003-01-28 17:39:25
Message-ID: x74r7tgomq.fsf@onceler.kciLink.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>>>>> "JH" == Jason Hihn <jhihn1(at)umbc(dot)edu> writes:

JH> Well this email is for everyone:
JH> 1) I don't want to PG dump because of 1) the time and 2) the space. If I
JH> did it that way, I might as well keep the old copy around and run diff

I don't know what you're doing, but my DB expanded out is about 18Gb.
The compressed dump is about 1.4Gb. To rsync the data takes about 4
hours over a private 100baseT switch not doing anything else. To
pg_dump takes about 40 minutes over the same wire.

The advantage is that the pg_dump is guaranteed consistent, no matter
how long it takes.

Here's how I pg_dump:

pg_dump -h dbhost -Fc DBNAME > DBNAME.`date +%d-%b-%Y`.dump

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D. Khera Communications, Inc.
Internet: khera(at)kciLink(dot)com Rockville, MD +1-240-453-8497
AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ayhan 2003-01-28 17:41:52 How "experimental" is PgSPI?
Previous Message Vivek Khera 2003-01-28 17:34:32 Re: all backends (pg7.2.3 / redhat 7.2) die due to unexpected signal 14 (SIGALRM)