Re: BUG #16132: PostgreSQL 12.1 and PLV8 2.3.13 => PostgreSQL crashes

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: james(dot)inform(at)pharmapp(dot)de, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16132: PostgreSQL 12.1 and PLV8 2.3.13 => PostgreSQL crashes
Date: 2019-11-25 03:41:32
Message-ID: 20191125034132.GH37821@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Nov 22, 2019 at 06:50:14PM +0000, PG Bug reporting form wrote:
> I am not sure if my issue is related to PostgreSQL or to the PLV8 extension.
>
> So I just post in case.
>
> I encountered the following severe issue. I am running PostgreSQL 12.1 on
> Ubuntu. Postgresql is build from source by myself, but the same issue
> appears when I am using Pg12.1 with Postgresapp on Mac.
> (www.postgresapp.com)
>
> I am using PLV8 Version 2.3.13.

Hard to say if this is something directly involving a change in
Postgres or something that plv8 does wrong with any new assumptions
taken in Postgres 12 code. FWIW, I have seen in the past as well
issues with PLv8 after upgrades to newer versions, and the fix
happened to be only needed in the PL. How does the trace look like?

For the note, I have noticed that you raised the same issue in the
upstream project:
https://github.com/plv8/plv8/issues/373
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2019-11-25 10:15:35 BUG #16135: `pgadmin4-web` package fails to update due to missing `pgadmin4-python3-flask-compress`
Previous Message Tom Lane 2019-11-24 23:45:28 Re: Precision/scale of a numeric attribute of a new data type are not handled correctly when the type is returned by a function