pg_extension_config_dump() doesn't register owned sequences
Is it intentional that pg_extension_config_dump() doesn't also add
sequences owned by a table? If not, I'll work on a patch.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Fri, Aug 28, 2015 at 10:16 AM, Jim Nasby <Jim.Nasby@bluetreble.com> wrote:
Is it intentional that pg_extension_config_dump() doesn't also add sequences
owned by a table? If not, I'll work on a patch.
I recall this behavior to be intentional. They are taken into account
only if they are explicitly marked with pg_extension_config_dump()
even in the case of SERIAL sequence, and when dumping the data those
sequences are updated with setval.
Regards,
--
Michael
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers