| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Rory Campbell-Lange <rory(at)campbell-lange(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: dump/restore problem due to CVE-2018-1058 (9.5.12) |
| Date: | 2018-04-08 18:15:07 |
| Message-ID: | 359c4b87-9c36-b251-f65c-fc9bcf2d4412@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 04/08/2018 11:01 AM, Rory Campbell-Lange wrote:
> Thanks for your comprehensive response, Adrian.
>
> Fair enough. It is however a tedious problem to resolve in a large
> code base and it would be cool to have a new "--set-search-path"
> option to pg_dump to override it.
From other posts that covered similar ground I would say other people
would agree. I am guessing the response you will get from those that can
make the changes is that would be just delaying the inevitable. You can
always ask though:)
>
> Thanks again
> Rory
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guyren Howe | 2018-04-08 21:39:49 | Rationale for aversion to the central database? |
| Previous Message | Rory Campbell-Lange | 2018-04-08 18:01:55 | Re: dump/restore problem due to CVE-2018-1058 (9.5.12) |