Re: BUG #16340: lo_manage() crashs DB instance

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: william(dot)crowell(at)openlogic(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16340: lo_manage() crashs DB instance
Date: 2020-04-03 14:40:13
Message-ID: 24271.1585924813@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message wcrowell 2020-04-03 15:02:20 Re: BUG #16340: lo_manage() crashs DB instance
Previous Message PG Bug reporting form 2020-04-03 14:02:01 BUG #16341: Installation with EnterpriseDB Community installer in NT AUTHORITY\SYSTEM context not possible