From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | s(dot)proels(at)pharmatechnik(dot)de |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #7567: Sequences not properly replicated |
Date: | 2012-09-25 16:08:47 |
Message-ID: | 21328.1348589327@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
s(dot)proels(at)pharmatechnik(dot)de writes:
> The following bug has been logged on the website:
> Bug reference: 7567
> Logged by: Stefan Prls
> Email address: s(dot)proels(at)pharmatechnik(dot)de
> PostgreSQL version: 9.1.3
> Operating system: OpenSUSE 11.4 32-Bit
> Description:
> Scenario:
> 1 Master, 1 Hot-Standby Slave, asynchronous streaming replication, both
> servers PostgreSQL 9.1.3.
The fact that the slave sees the last_value as ahead of the master is
not a bug; you'd have the same last_value on the master if it were to
crash and restart. (This is due to a tradeoff made long ago to reduce
the amount of WAL traffic created by nextval: only one WAL record is
written per 32 nextval's, and that record claims last_value is 32 ahead
of what it previously was.)
There is a known bug, fixed in 9.1.5, associated with sequences that
have been ALTER'd ... but that's not what you're showing here.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Dimitri Fontaine | 2012-09-25 16:29:17 | Re: BUG #6704: ALTER EXTENSION postgis SET SCHEMA leaves dangling relations |
Previous Message | Fujii Masao | 2012-09-25 14:10:17 | Re: BUG #7533: Client is not able to connect cascade standby incase basebackup is taken from hot standby |