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

Re: [GENERAL] pg_migrator not setting values ofsequences?

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>, 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 ofsequences?
Date: 2009-07-15 16:23:08
Message-ID: 20090715162308.GI4551@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackers
Tom Lane wrote:
> 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 :-(

It seems cleaner to have a pg_dump --dump-all-sequences or some such.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

pgsql-hackers by date

Next:From: Simon RiggsDate: 2009-07-15 16:27:54
Subject: Re: hot standby - merged up to CVS HEAD
Previous:From: Tom LaneDate: 2009-07-15 16:17:29
Subject: Re: Add encoding support to COPY

pgsql-general by date

Next:From: Alvaro HerreraDate: 2009-07-15 16:28:57
Subject: Re: [GENERAL] large object does not exist afterpg_migrator
Previous:From: Tom LaneDate: 2009-07-15 16:10:41
Subject: Re: [GENERAL] pg_migrator not setting values of sequences?

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