Re: Howto: Using PITR recovery for standby replication
От | Benjamin Krajmalnik |
---|---|
Тема | Re: Howto: Using PITR recovery for standby replication |
Дата | |
Msg-id | 8511B4970E0D124898E973DF496F9B4357E0F7@stash.stackdump.local обсуждение исходный текст |
Ответ на | Slony1 or DRBD for replication ? (Pierre LEBRECH <pierre.lebrech@laposte.net>) |
Ответы |
Re: Howto: Using PITR recovery for standby replication
|
Список | pgsql-admin |
From: Alvaro Herrera [mailto:alvherre@commandprompt.com]
Sent: Thu 4/20/2006 10:02 PM
To: Benjamin Krajmalnik
Cc: Tom Lane; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Howto: Using PITR recovery for standby replication
Benjamin Krajmalnik wrote:
> The particular table which was problematic (and for which I posted
> another message due to the unique constraint violation which I am
> seeing intermittently) is the one with the high insertion rate. The
> sequence is currently being used to facilitate purginf of old records.
How are you creating the dumps of the sequence and the table? If you do
both separately (as in two pg_dump invocations with a -t switch each),
that could explain your problem. This shouldn't really happen however,
because the sequence dump should be emitted in a dump of the table, if
the field is really of SERIAL or BIGSERIAL type. However I don't see
any other way which would make the sequence go out of sync.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
В списке pgsql-admin по дате отправления: