Re: BUG #2552: wrong sql dump?

Try using pg_dump from 8.1.4, which is the recommended procedure for
upgrading. You might have to go to an intermediate version first,
such as 7.4.13.

On Jul 26, 2006, at 11:15 AM, Boris wrote:

>
> 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. :)
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>

--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461