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: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: 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-13 23:18:09
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-generalpgsql-hackers
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Tilmann Singer wrote:
>> However, all of the sequences were at the initial values and not
>> bumped up to the last used value as I would have expected. The first
>> nextval call on any sequence in the migrated 8.4 database always
>> returned 1.

> Wow, that is also surprising.  I am going to have to run some tests to
> find the cause, but it certainly is not intended.

Looks like pg_migrator neglects to include relkind 'S' in the set of
tables that it needs to physically migrate.

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: KaiGai KoheiDate: 2009-07-13 23:21:54
Subject: Re: [PATCH] SE-PgSQL/lite rev.2163
Previous:From: Bruce MomjianDate: 2009-07-13 23:02:43
Subject: Re: Alpha release process

pgsql-general by date

Next:From: Alvaro HerreraDate: 2009-07-14 00:28:58
Subject: Re: [GENERAL] large object does not exist afterpg_migrator
Previous:From: Bruce MomjianDate: 2009-07-13 22:38:13
Subject: Re: [GENERAL] large object does not exist after pg_migrator

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