On Wednesday 14 September 2005 16:18, you wrote:
Robert Bernier wrote:
>What are the issues, of adding tables to a set using the "set add table"
> but NOT "set add sequence" for sequences that the tables use such as for
> example serial data-types i.e. the sequences are already created and
> initialized to the correct value for each and every node?
>

If you don't add the sequence in, then if you subsequently switch the
origin to a new node, it won't know about the sequence updates, and will
presumably imagine it should start numbering things somewhere earlier.


You'll start seeing primary key violations in cases where the sequence
is used to populate a PK field.

The "danger" case is where a sequence is used in a more subtle fashion
such as to refer to some sort of common across-multiple-tables
transaction ID.  We once ran into a case where a sequence of that sort
was handled wrongly and it caused a veritable plague of billing problems
as unrelated transactions started linking to one another :-(.

-- 
Robert Bernier
PostgreSQL Business Intelligence Analyst
SRA AMERICA (Formerly of One WTC)
PostgreSQL Services:Consulting,Migration,Support and Training
One Penn Plaza, Suite 1910
New York, NY 10119

Tel: ?212.244.8833 ext:22

www.sraapowergres.com ?robertb at sraapowergres.com
www.sraamerica.com