Re: pg_dump and search_path

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

Steve Thames wrote:
> 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.

You can tell for sure by setting log_statement=all.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2015-08-11 19:03:57 Re: How to compare different datums within from a tuple?
Previous Message Peter Eisentraut 2015-08-11 18:35:49 Re: WIP: SCRAM authentication