From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Tilmann Singer <tils(at)tils(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [GENERAL] pg_migrator not setting values of sequences? |
Date: | 2009-07-15 16:10:41 |
Message-ID: | 23975.1247674241@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> writes:
> I think you don't need transfer sequence table, because pg_dump should
> create DDL command (CREATE SEQUENCE) which should create new nice
> sequence relation.
Yeah, but pg_dump is doing a schema-only dump so it doesn't transfer the
current state of the sequence.
The most effective solution might be to revert the change in pg_migrator
and instead have pg_dump interpret --binary-upgrade --schema-only to
include the data for sequences. It seems ugly as sin though :-(
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2009-07-15 16:23:08 | Re: [GENERAL] pg_migrator not setting values of sequences? |
Previous Message | Tom Lane | 2009-07-15 16:05:38 | Re: initdb --locale=LATIN1 fails on Windows |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-07-15 16:17:29 | Re: Add encoding support to COPY |
Previous Message | David Blewett | 2009-07-15 16:08:32 | Re: Add encoding support to COPY |