From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Aleksander Alekseev <aleksander(at)timescale(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Sven Klemm <sven(at)timescale(dot)com> |
Subject: | Re: [PATCH] Fix memory corruption in pg_shdepend.c |
Date: | 2021-10-21 14:55:02 |
Message-ID: | 202110211455.nallnmm5gavd@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2021-Oct-21, Michael Paquier wrote:
> On Wed, Oct 20, 2021 at 09:19:51AM -0300, Alvaro Herrera wrote:
> > Ouch ... this means that pg_shdepends contents are broken for databases
> > created with 14.0? hmm ... yes.
>
> Yes, it means so :(
For the upcoming release notes in 14.1 I think we'd do well to document
how to find out if you're affected by this; and if you are, how to fix
it.
I suppose pg_describe_object can be used on the contents of pg_shdepend
to detect it. I'm less sure what to do to correct it -- delete the
bogus entries and regenerate them with some bulk query?
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"Ninguna manada de bestias tiene una voz tan horrible como la humana" (Orual)
From | Date | Subject | |
---|---|---|---|
Next Message | Bharath Rupireddy | 2021-10-21 14:55:06 | Re: wait event and archive_command |
Previous Message | Tom Lane | 2021-10-21 14:53:58 | Re: Assorted improvements in pg_dump |