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

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(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-14 02:37:02
Message-ID: 200907140237.n6E2b2x27210@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Tom Lane wrote:
> 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.

Thanks, I have fixed pg_migrator with the attached patch. Once we find
the cause of the lovacuum problem, I will make a new pg_migrator release.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

Attachment Content-Type Size
/rtmp/diff text/x-diff 916 bytes

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2009-07-14 03:03:04 Re: [GENERAL] large object does not exist after pg_migrator
Previous Message Andreas 2009-07-14 00:54:44 Flexibility of views and functions?

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-07-14 02:42:53 Re: Upgrading our minimum required flex version for 8.5
Previous Message Bruce Momjian 2009-07-14 00:36:22 Re: [GENERAL] large object does not exist after pg_migrator