Re: [GENERAL] db replication and errors

Benjamin wrote: Thanx for the pointers, Richard. If the async feature is used on the primary, shud we copy on the xlog and clog files onto the backup as well? What is the "async feature"? I meant fsync. I meant to ask, if FSYNC is enabled, is all pending data written onto the disk? Yes. Turn it

Re: [GENERAL] db replication and errors

Thanx for the pointers, Richard. If the async feature is used on the primary, shud we copy on the xlog and clog files onto the backup as well? What is the "async feature"? I meant fsync. I meant to ask, if FSYNC is enabled, is all pending data written onto the disk? As of now, we shut down pos

Re: [GENERAL] db replication and errors

Benjamin wrote: Hello everyone, The scene : Currently, we r using, Postgresql v 7.3, on RedHat 9 machines. We provide a hot standby at all times for the Primary server. So, we have to maintain a duplicate of the entire database. The problem arises, when the standby boots. I wanted to know, whenev

[GENERAL] db replication and errors

Hello everyone, The scene : Currently, we r using, Postgresql v 7.3, on RedHat 9 machines. We provide a hot standby at all times for the Primary server. So, we have to maintain a duplicate of the entire database. The problem arises, when the standby boots. I wanted to know, whenever the standby b