Re: pg_dump and search_path

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Steve Thames <sthames42(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_dump and search_path
Date: 2015-08-11 17:41:15
Message-ID: 26351.1439314875@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Steve Thames 2015-08-11 17:59:36 Re: pg_dump and search_path
Previous Message Alvaro Herrera 2015-08-11 17:31:20 Re: pg_dump and search_path