pg_dump sequence problem - Mailing list pgsql-general

From Q Beukes
Subject pg_dump sequence problem
Date
Msg-id 44D33E94.3010100@list.za.net
Whole thread Raw
Responses Re: pg_dump sequence problem  ("Nikolay Samokhvalov" <samokhvalov@gmail.com>)
Re: pg_dump sequence problem  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hey,

Is this a bug or a feature (PG 8.1.3)?

If have a two schemas called: cbt and core.
I have a sequence: core.invoicesids_seq.
I have a couple of tables in cbt having columns with defaults:
nextval('core.invoicesids_seq')

When I dump the database, the tables dumped for "cbt" dont have alter
commands to set the default values to
"nextval('core.invoicesids_seq')" again. Those columns are simply
created as serial fields, and their values set to "1, false".

So when I restore the database, it is not what it was, which makes
restoring backups quite an effort.


regards
Q Beukes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iQEVAwUBRNM+lLEDZDQ16UzTAQIBIggAv3XxXa2HZ4ZU0i0Zu738r4567cgk5trr
/ZGLCdXOSY2wvOtSDtsAVD/rMZXwPEsPfy4M2u0inllr0Uq2uQ1pA4/+fohtqPq5
XPCv5G3wLFcOJR7NpjKAjRC5sl+1/xesskPf174W64RC+iZJJr/Y5GSFffUvkcQY
hTpEC/GhENXEgnMovZTlOyXu+b/VCQt0gndpbGPObP1+XYAbN8QZYwe29MmKxMLK
aIhL/7yV/vfddozjdWVaQzj0RH4ZuZ4JwbGP5iqGohhACrUCuy26qJJOAH1gYXh5
vH3JlLZ3mRyF/0GDNWNISjOzGFIVcrQSwNO0o6SRPyd+m0Og2oC+8Q==
=4eC2
-----END PGP SIGNATURE-----


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Locale/encoding problem/question
Next
From: "Merlin Moncure"
Date:
Subject: Re: Best Procedural Language?