Skip site navigation (1) Skip section navigation (2)

Re: [GENERAL] pg_migrator not setting values of sequences?

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 (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-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

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2009-07-15 16:17:29
Subject: Re: Add encoding support to COPY
Previous:From: David BlewettDate: 2009-07-15 16:08:32
Subject: Re: Add encoding support to COPY

pgsql-general by date

Next:From: Alvaro HerreraDate: 2009-07-15 16:23:08
Subject: Re: [GENERAL] pg_migrator not setting values ofsequences?
Previous:From: Tom LaneDate: 2009-07-15 16:05:38
Subject: Re: initdb --locale=LATIN1 fails on Windows

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group