"Joshua L. San Juan" <[EMAIL PROTECTED]> writes:
> but in the second table - the sequence was incorrect:
> SELECT pg_catalog.setval ('table2_id_seq', 1, true);

It seems fairly hard to believe that what pg_dump emitted was not the
actual state of the sequence object.  Why do you think this is incorrect?

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match

Reply via email to