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

BUG #2552: wrong sql dump?

From: "Boris" <b(dot)koshevoy(at)vk-brok(dot)kiev(dot)ua>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #2552: wrong sql dump?
Date: 2006-07-26 11:15:49
Message-ID: 200607261115.k6QBFn45087753@wwwmaster.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      2552
Logged by:          Boris
Email address:      b(dot)koshevoy(at)vk-brok(dot)kiev(dot)ua
PostgreSQL version: 8.1.4
Operating system:   win 2000
Description:        wrong sql dump?
Details: 

Hi!

data base lives from pg7.2
before upgrade to 8.1.2 I used pgdump from 7.2
then I go to pg 8.1.4 and pgAdmin III 1.4.3 (Jul 19 2006)

The sequence for primry key (PK) of some (not all) was missed and PK become
wrong - allways 0.

I export all base as sql script (1).

When I import this script I see no sequences for sope PK.

I see no commands to create sequences in this (1)sql script.

ForEx: table "auth"."access_policy_list" has a PK but no sequence is
created.

See sql dump here http://www.bdr.kiev.ua/tmpboris/bdr_v0_plain.zip

ICQ 176869864 for any more info, please. :)

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2006-07-26 15:09:41
Subject: Re: BUG #2550: pg_dumpall 7.4.13 -> restore 8.1.4 problem
Previous:From: Zuleima LaraDate: 2006-07-25 16:24:54
Subject: BUG #2551: to_char a to_number

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