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

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(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-18 15:58:27
Message-ID: 200907181558.n6IFwRC10882@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera wrote:
> Bruce Momjian wrote:
>
> > Something is certainly wrong. Did we change sequence table format from
> > 8.3 to 8.4?
>
> 8.3 does not have start_value.

Looking at an invalidly-migrated sequence's columns:

regression=> \d serialtest_f2_foo
Sequence "public.serialtest_f2_foo"
Column | Type | Value
---------------+---------+---------------------
sequence_name | name | serialtest_f2_foo
last_value | bigint | 3
start_value | bigint | 1
increment_by | bigint | 9223372036854775807
max_value | bigint | 1
min_value | bigint | 1
cache_value | bigint | 0
log_cnt | bigint | 25387551686912
is_cycled | boolean | f
is_called | boolean |

Should pg_migrator just pull the misaligned values and do an ALTER
SEQUENCE/seval() to fix it, or create a script to do that?

--
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. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2009-07-18 16:06:00 SE-PostgreSQL?
Previous Message Tom Lane 2009-07-18 15:48:14 GEQO vs join order restrictions