Re: Using RSYNC for replication?
От | Arjen van der Meijden |
---|---|
Тема | Re: Using RSYNC for replication? |
Дата | |
Msg-id | 000f01c2c6ff$49e8d130$3ac15e91@acm обсуждение исходный текст |
Ответ на | Re: Using RSYNC for replication? (Vivek Khera <khera@kcilink.com>) |
Список | pgsql-general |
You can do without the temporal filestorage, using unix/linux' pipe functionality: pg_dump whatever_commands -you -want | psql -h remotehost -etc Or, when dumping with the binary format, pipe it to pg_restore (afaik that is possible) Arjen > -----Oorspronkelijk bericht----- > Van: pgsql-general-owner@postgresql.org > [mailto:pgsql-general-owner@postgresql.org] Namens Vivek Khera > Verzonden: dinsdag 28 januari 2003 18:39 > Aan: pgsql-general@postgresql.org > Onderwerp: Re: [GENERAL] Using RSYNC for replication? > > > >>>>> "JH" == Jason Hihn <jhihn1@umbc.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. > JH> 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@kciLink.com Rockville, MD +1-240-453-8497 > AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/ > > ---------------------------(end of > broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > http://www.postgresql.org/users-lounge/docs/faq.html
В списке pgsql-general по дате отправления: