From: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
---|---|
To: | "Blake McBride" <blake(at)mcbride(dot)name> |
Cc: | "rob stone" <floriparob(at)gmail(dot)com>,pgsql-general(at)postgresql(dot)org |
Subject: | Re: Must re-connect to see tables |
Date: | 2018-03-27 12:31:32 |
Message-ID: | 28f543ea-acce-4376-b237-8a02f8a54fee@manitou-mail.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Blake McBride wrote:
> data.sql is an untouched dump of a database from PostgreSQL 9.5.12.
>
> The import seems to have worked. I just need another \c after the \i.
An effect of reconnecting is to reset the search_path to what
it was before including your dump file.
You're most certainly affected by the search_path-related
changes in pg_dump done in the latest versions following
CVE-2018-1058
See https://www.postgresql.org/support/security/
or
https://www.postgresql.org/about/news/1834/
Manually issuing
RESET search_path;
after \i data.sql should get "public" back in the search_path
without reconnecting and after that \dt would work as usual.
Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Dearman | 2018-03-27 13:54:44 | logical decoder lsn order between transactions |
Previous Message | Blake McBride | 2018-03-27 12:16:01 | Re: Must re-connect to see tables |