Dear all,
Thank you so much for your response to my request for information.
I appreciated you taking the time to provide some answers and for getting back
to me so promptly.
It made a lot of sense and was exactly what I needed to know.
At 2022-08-25 12:19:03, "Adrian Klaver" wrote:
>On 8/24/
On 8/24/22 20:39, gzh wrote:
Hi Tom,
Thank you for your prompt response.
When I use pg_dump to export schema from an older version of PostgreSQL
8.2.3 , it adds the following line at the beginning:
SET search_path = public, pg_catalog;
Is it possible set an option where pg_dump will add thi
On Wednesday, August 24, 2022, gzh wrote:
>
> When I use pg_dump to export schema from an older version of PostgreSQL
> 8.2.3 , it adds the following line at the beginning:
>
> SET search_path = public, pg_catalog;
>
> Is it possible set an option where pg_dump will add this line in
> PostgreSQL 1
Hi Tom,
Thank you for your prompt response.
When I use pg_dump to export schema from an older version of PostgreSQL 8.2.3 ,
it adds the following line at the beginning:
SET search_path = public, pg_catalog;
Is it possible set an option where pg_dump will add this line in PostgreSQL
12.5?
A
gzh writes:
> When I use pg_dump to export schema from a database, it adds the following
> line at the beginning:
> SELECT pg_catalog.set_config('search_path', '', false);
> Is it possible set an option where pg_dump will not add this line?
No. It's a security precaution.
> It is causing issu
When I use pg_dump to export schema from a database, it adds the following line
at the beginning:
SELECT pg_catalog.set_config('search_path', '', false);
Is it possible set an option where pg_dump will not add this line?
It is causing issues later when I try to execute other SQL commands
