On Thu, Oct 13, 2011 at 4:20 PM, Merlin Moncure mmonc...@gmail.com wrote:
On Thu, Oct 13, 2011 at 4:07 PM, Bob Hatfield bobhatfi...@gmail.com wrote:
have you had any power events? hard shutdowns, etc? I wonder if the
problem is in the clog files, and not the heap itself.
Nothing unusual for
Any movement on this? There is considerable interest in any known
issues resolving reproducible issues with postgres replication. Do
you happen to remember if set up the standby when the master was under
high load conditions? Any interesting/unexplained messages in the
standby logs?
I'm
On Wed, Oct 12, 2011 at 5:17 PM, Bob Hatfield bobhatfi...@gmail.com wrote:
Something about your setup is suspect. Disks perhaps.
Disk: Fusion IOdrive (1.2TB NAND drive)
I've read that one should set wal_sync_method=fsync_writethrough for
Windows servers. It's currently set to open_datasync,
have you had any power events? hard shutdowns, etc? I wonder if the problem
is in the clog files, and not the heap itself.
Nothing unusual for as long as I can tell. Reminder that as long as I
don't restart the primary's pg process, everything works fine
(secondary's data is intact).
It's
On Thu, Oct 13, 2011 at 4:07 PM, Bob Hatfield bobhatfi...@gmail.com wrote:
have you had any power events? hard shutdowns, etc? I wonder if the problem
is in the clog files, and not the heap itself.
Nothing unusual for as long as I can tell. Reminder that as long as I
don't restart the
Should replication cause corruption on the secondary when stopping/starting
the primary?
I wasn't aware 8.3 had any built in replication? what sort of replication
add-ons are you using?
Continuous archiving / WAL shipping as described in:
On Tue, Oct 11, 2011 at 12:12 AM, Bob Hatfield bobhatfi...@gmail.com wrote:
Should replication cause corruption on the secondary when stopping/starting
the primary? (pg 8.3.12, windows 2008 R2 on both servers)
No, it shouldn't. Any duplicate keys would represent a serious error.
It sounds
Should replication cause corruption on the secondary when stopping/starting
the primary?
I wasn't aware 8.3 had any built in replication? what sort of replication
add-ons are you using?
Continuous archiving / WAL shipping as described in:
Should replication cause corruption on the secondary when stopping/starting
the primary? (pg 8.3.12, windows 2008 R2 on both servers)
No, it shouldn't. Any duplicate keys would represent a serious error.
It sounds like you're using warm standby, but when you say run
pg_start_backup() AFTER
On Wed, Oct 12, 2011 at 10:51 PM, Bob Hatfield bobhatfi...@gmail.com wrote:
Should replication cause corruption on the secondary when stopping/starting
the primary? (pg 8.3.12, windows 2008 R2 on both servers)
No, it shouldn't. Any duplicate keys would represent a serious error.
It sounds
Something about your setup is suspect. Disks perhaps.
Disk: Fusion IOdrive (1.2TB NAND drive)
I've read that one should set wal_sync_method=fsync_writethrough for
Windows servers. It's currently set to open_datasync, I have no idea
what effect that will have other than I've read less
Should replication cause corruption on the secondary when stopping/starting
the primary? (pg 8.3.12, windows 2008 R2 on both servers)
Everything seems to work OK, but when we trigger the replication server, it
doesn’t pass a reindex. (Errors with can’t create unique indexes due to
duplicate
On 10/10/11 4:12 PM, Bob Hatfield wrote:
Should replication cause corruption on the secondary when
stopping/starting the primary?
I wasn't aware 8.3 had any built in replication? what sort of
replication add-ons are you using?
--
john r pierceN 37, W 122
santa
13 matches
Mail list logo
