| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
| Cc: | "Efrain J(dot) Berdecia" <ejberdecia(at)yahoo(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17229: Segmentation Fault after upgrading to version 13 |
| Date: | 2021-10-25 23:28:51 |
| Message-ID: | 24187.1635204531@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Alexander Korotkov <aekorotkov(at)gmail(dot)com> writes:
> On Mon, Oct 25, 2021 at 4:49 PM Efrain J. Berdecia <ejberdecia(at)yahoo(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2021-10-25 23:29:23 | BUG #17247: How to avoid crating multiple Foreign keys on same column on same table. |
| Previous Message | Alexander Korotkov | 2021-10-25 23:20:59 | Re: BUG #17229: Segmentation Fault after upgrading to version 13 |