| 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: | 2929.1247527089@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2009-07-14 00:28:58 | Re: [GENERAL] large object does not exist after pg_migrator |
| Previous Message | Bruce Momjian | 2009-07-13 22:38:13 | Re: [GENERAL] large object does not exist after pg_migrator |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | KaiGai Kohei | 2009-07-13 23:21:54 | Re: [PATCH] SE-PgSQL/lite rev.2163 |
| Previous Message | Bruce Momjian | 2009-07-13 23:02:43 | Re: Alpha release process |