Re: BUG #17229: Segmentation Fault after upgrading to version 13 - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #17229: Segmentation Fault after upgrading to version 13
Date
Msg-id 24187.1635204531@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #17229: Segmentation Fault after upgrading to version 13  (Alexander Korotkov <aekorotkov@gmail.com>)
Responses Re: BUG #17229: Segmentation Fault after upgrading to version 13
List pgsql-bugs
Alexander Korotkov <aekorotkov@gmail.com> writes:
> On Mon, Oct 25, 2021 at 4:49 PM Efrain J. Berdecia <ejberdecia@yahoo.com> wrote:
>> On a separate note, applying 13.4 on a running cluster caused some issues with;
>> "could not load library "/usr/pgsql-13/lib/plpgsql.so": /usr/pgsql-13/lib/plpgsql.so: undefined symbol:
EnsurePortalSnapshotExists"

That sounds a lot like the OP hadn't actually restarted the server,
or at least not right away.  A 13.4 plpgsql.so loading into a 13.3
server would do that.

> Not sure what is our policy on introducing incompatibilities between
> extensions and postgres binary in minor releases...

We've done that before, we'll do it again.  You can't realistically
fix many bugs without adding new functions.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: BUG #17229: Segmentation Fault after upgrading to version 13
Next
From: PG Bug reporting form
Date:
Subject: BUG #17247: How to avoid crating multiple Foreign keys on same column on same table.