log shipping and nextval sequences

Поиск
Список
Период
Сортировка
От Leonardo Cezar
Тема log shipping and nextval sequences
Дата
Msg-id 2315783e0908051159t7af908f0kd2aa4b4bcef00327@mail.gmail.com
обсуждение исходный текст
Ответы Re: log shipping and nextval sequences  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Hi,

In warm standby system when we have a filled log segment forwarded to
archiving, there is an inconsistency on standby next value sequences
obtained by a call to nextval() function. e.g.:

* Primary server
- Create sequence seq_a;
- Select nextval ( 'seq_a'); # value 1;
- Log shipping;

* Standby server
- Failover;
- Select nextval ( 'seq_a') on standby # value = currval + 31 (written ahead)

AFAIK this occurs because some fetches (log_cnt) are made in advance
and they are recorded in the log and shipping together.
Does it necessary for some kind of overhead or something like that?

Does it make sense to create a GUC  to control the log_cnt amount
rather than SEQ_LOG_VALS approach?

version: 8.3.7

regards,

-Leo
-- 
Leonardo Cezar
http://postgreslogia.wordpress.com
http://www.dextra.com.br/postgres


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Josh Berkus
Дата:
Сообщение: Re: GRANT ON ALL IN schema
Следующее
От: Robert Haas
Дата:
Сообщение: Re: CommitFest 2009-07: Closing Soon