Re: performance hit for replication
От | Dave Page |
---|---|
Тема | Re: performance hit for replication |
Дата | |
Msg-id | E7F85A1B5FF8D44C8A1AF6885BC9A0E472C171@ratbert.vale-housing.co.uk обсуждение исходный текст |
Ответ на | performance hit for replication ("Matthew Nuzum" <matt.followers@gmail.com>) |
Список | pgsql-performance |
> -----Original Message----- > From: pgsql-performance-owner@postgresql.org > [mailto:pgsql-performance-owner@postgresql.org] On Behalf Of > Matthew Nuzum > Sent: 12 April 2005 17:25 > To: pgsql-performance@postgresql.org > Subject: [PERFORM] performance hit for replication > > So, my question is this: My server currently works great, > performance wise. > I need to add fail-over capability, but I'm afraid that introducing a > stressful task such as replication will hurt my server's > performance. Is > there any foundation to my fears? I don't need to replicate > the archived log > data because I can easily restore that in a separate step > from the nightly > backup if disaster occurs. Also, my database load is largely > selects. My > application works great with PostgreSQL 7.3 and 7.4, but I'm > currently using > 7.3. If it's possible to upgrade to 8.0 then perhaps you could make use of PITR and continuously ship log files to your standby machine. http://www.postgresql.org/docs/8.0/interactive/backup-online.html I can't help further with this as I've yet to give it a go myself, but others here may have tried it. Regards, Dave.
В списке pgsql-performance по дате отправления: