Re: Using RSYNC for replication?
От | Vivek Khera |
---|---|
Тема | Re: Using RSYNC for replication? |
Дата | |
Msg-id | x74r7tgomq.fsf@onceler.kciLink.com обсуждение исходный текст |
Ответ на | Re: Using RSYNC for replication? (Jason Hihn <jhihn1@umbc.edu>) |
Ответы |
Re: Using RSYNC for replication?
|
Список | pgsql-general |
>>>>> "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. 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/
В списке pgsql-general по дате отправления: