log shipping and nextval sequences

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