Horton

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

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: william.crowell@openlogic.com
Cc: pgsql-bugs@lists.postgresql.org
Date: 2020-04-03T14:40:13Z
Lists: pgsql-bugs 
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

Commits

  1. Fix bogus CALLED_AS_TRIGGER() defenses.