On Thu, Jul 13, 2023 at 2:00 PM Gurjeet Singh <gurj...@singh.im> wrote:
> On Thu, Jul 13, 2023 at 1:37 PM David G. Johnston > <david.g.johns...@gmail.com> wrote: > > > > I'm against simply breaking the past without any recourse as what we > did for pg_dump/pg_restore still bothers me. > > I'm sure this is tangential, but can you please provide some > context/links to the change you're referring to here. > > Here is the instigating issue and a discussion thread on the aftermath: https://wiki.postgresql.org/wiki/A_Guide_to_CVE-2018-1058%3A_Protect_Your_Search_Path https://www.postgresql.org/message-id/flat/13033.1531517020%40sss.pgh.pa.us#2aa2e25816d899d62f168926e3ff17b1 David J.