Re: pg_dump and search_path

Thank you gentlemen for clarifying this.

I found this problem when my database modeling tool saw a change in the
database (the nextval() parameters) after a database restore.
I guess the tool must be reading adsrc for this information.

Cheers,
Steve Thames

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Tuesday, August 11, 2015 10:41 AM
To: Alvaro Herrera
Cc: Steve Thames; pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] pg_dump and search_path

Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> Don't ever rely on adsrc. It's useless. Use pg_get_expr(adbin)
> instead. That's safe, for instance, if the sequence gets renamed.

It's probably past time we got rid of that column altogether. It just
wastes space and cycles. There was an argument for not being too quick to
get rid of it, but we deprecated it in 7.2 ... surely people have had more
than enough time to fix their applications.

regards, tom lane