On Sat, Mar 31, 2012 at 6:58 PM, Andreas wrote:
>
>
> Now what could one do to prevent those sequence gaps?
> There might be scenarios where it's important not to have gaps in the
> numbering even when one has to switch to the standby if there is a failiour
> on the master.
> E.g. numbers of invo
Am 31.03.2012 23:38, schrieb Tom Lane:
Andreas writes:
Now I added 1 row on the master.
Before both sequence start values were 403.
After the insert the master shows 404 as expected but the "hot-standby"
shows 436.
What are you doing to get it to "show" a value --- not nextval(),
presumably?
Andreas writes:
> Now I added 1 row on the master.
> Before both sequence start values were 403.
> After the insert the master shows 404 as expected but the "hot-standby"
> shows 436.
What are you doing to get it to "show" a value --- not nextval(),
presumably?
I think that this may be the exp
Now I added 1 row on the master.
Before both sequence start values were 403.
After the insert the master shows 404 as expected but the "hot-standby"
shows 436.
In the slaves table there is only the one row more, I just inserted on
the master and it's ID column shows 404.
Lets suppose - and h
Hi,
I configured a master and a hot-standby server as described here:
http://wiki.postgresql.org/wiki/Binary_Replication_Tutorial#Starting_Replication_with_only_a_Quick_Master_Restart
At first everything looked ok.
Then some days later I find that at least some sequences on the
hot-standby are h
