From: | gzh <gzhcoder(at)126(dot)com> |
---|---|
To: | "Adrian Klaver" <adrian(dot)klaver(at)aklaver(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, david(dot)g(dot)johnston(at)gmail(dot)com |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re:Re: pg_dump without setting search_path |
Date: | 2022-08-25 05:56:03 |
Message-ID: | 84f48ce.353d.182d3926553.Coremail.gzhcoder@126.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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" <adrian(dot)klaver(at)aklaver(dot)com> wrote:
>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 this line in
>> PostgreSQL 12.5?
>>
>
>No for this reason:
>
>https://wiki.postgresql.org/wiki/A_Guide_to_CVE-2018-1058:_Protect_Your_Search_Path
>
>>> regards, tom lane
>
>
>--
>Adrian Klaver
>adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Bryn Llewellyn | 2022-08-25 06:50:14 | Re: Two questions about "pg_constraint" |
Previous Message | Alexander Kukushkin | 2022-08-25 05:23:17 | Re: Unable to start replica after failover |