From: Tom Lane <tgl@sss.pgh.pa.us>
To: william.crowell@openlogic.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16340: lo_manage() crashs DB instance
Date: Fri, 03 Apr 2020 10:40:13 -0400
Message-ID: <24271.1585924813@sss.pgh.pa.us> (raw)
In-Reply-To: <16340-591c7449dc7c8c47@postgresql.org>
References: <16340-591c7449dc7c8c47@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> PostgreSQL crashes if you do the following:
> $psql postgres -c 'create extension lo'
> CREATE EXTENSION
> $psql postgres -c 'select lo_manage()'
> server closed the connection unexpectedly
Huh, somebody was a bit too cute here:
if (!CALLED_AS_TRIGGER(fcinfo)) /* internal error */
elog(ERROR, "%s: not fired by trigger manager",
trigdata->tg_trigger->tgname);
Will fix, thanks for the report!
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, william.crowell@openlogic.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16340: lo_manage() crashs DB instance
In-Reply-To: <24271.1585924813@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox