From: Tom Lane <tgl@sss.pgh.pa.us>
To: subi.the.dream.walker@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18225: chdb's s3 table function crashes postgresql with
 plpython3
In-reply-to: <18225-9acc648b45a1a6a2@postgresql.org>
References: <18225-9acc648b45a1a6a2@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Mon, 04 Dec 2023 13:47:24 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <755705.1701701602.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 04 Dec 2023 09:53:22 -0500
Message-ID: <755706.1701701602@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/755706.1701701602%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> The following anonymous block causes a server termination:
> =3D=3D=3D=3D=3D=3D=3D =

> do language plpython3u $$
> import chdb
> chdb.query(sql=3D'''select * from
> s3('https://datasets-documentation.s3.eu-west-3.amazonaws.com/aapl_stock=
.csv')
> limit 10''')
> $$
> =3D=3D=3D=3D=3D=3D=3D

> The related logs:
> =3D=3D=3D=3D=3D=3D=3D
> 2023-12-04 13:36:28.086 UTC [3202531] LOG:  server process (PID 3216826)=
 was
> terminated by signal 6: Aborted

The useful details would have appeared *before* this message.
Look for TRAP: lines, or possibly python-generated messages.
(This could easily have been a python-internal abort, rather
than anything Postgres did.)  Also there might be a stack trace.

			regards, tom lane