pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #16340: lo_manage() crashs DB instance
3+ messages / 3 participants
[nested] [flat]
Commits from this thread:
2020-04-03 6dd9f35779 d56657c35d 7b15522834 a9f821f488 82bc56e633 85f0d47038 Fix bogus CALLED_AS_TRIGGER() defenses.
* BUG #16340: lo_manage() crashs DB instance
@ 2020-04-03 13:46 PG Bug reporting form <noreply@postgresql.org>
2020-04-03 14:40 ` Re: BUG #16340: lo_manage() crashs DB instance Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 3+ messages in thread
From: PG Bug reporting form @ 2020-04-03 13:46 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org; +Cc: william.crowell@openlogic.com
The following bug has been logged on the website:
Bug reference: 16340
Logged by: William Crowell
Email address: william.crowell@openlogic.com
PostgreSQL version: 11.7
Operating system: RHEL 7.7
Description:
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
This probably means the server terminated abnormally
before or while processing the request.
connection to server was lost
...
2020-04-02 13:42:23 CEST / postgres / xxxx / 1043 / 00000 / [local]] - LOG:
AUDIT: SESSION,1,2,FUNCTION,EXECUTE,FUNCTION,public.lo_manage,select
lo_manage(),<none>
[2020-04-02 13:42:23 CEST / / / 24618 / 00000 / ] - LOG: server process
(PID 1043) was terminated by signal 11: Segmentation fault
[2020-04-02 13:42:23 CEST / / / 24618 / 00000 / ] - DETAIL: Failed
process was running: select lo_manage()
[2020-04-02 13:42:23 CEST / / / 24618 / 00000 / ] - LOG: terminating any
other active server processes
I do know that lo_manage requires an argument, but it should not create a
segmentation fault even though the argument is not provided.
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: BUG #16340: lo_manage() crashs DB instance
2020-04-03 13:46 BUG #16340: lo_manage() crashs DB instance PG Bug reporting form <noreply@postgresql.org>
@ 2020-04-03 14:40 ` Tom Lane <tgl@sss.pgh.pa.us>
2020-04-03 15:02 ` Re: BUG #16340: lo_manage() crashs DB instance wcrowell <wcrowell@perforce.com>
0 siblings, 1 reply; 3+ messages in thread
From: Tom Lane @ 2020-04-03 14:40 UTC (permalink / raw)
To: william.crowell@openlogic.com; +Cc: pgsql-bugs@lists.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
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: BUG #16340: lo_manage() crashs DB instance
2020-04-03 13:46 BUG #16340: lo_manage() crashs DB instance PG Bug reporting form <noreply@postgresql.org>
2020-04-03 14:40 ` Re: BUG #16340: lo_manage() crashs DB instance Tom Lane <tgl@sss.pgh.pa.us>
@ 2020-04-03 15:02 ` wcrowell <wcrowell@perforce.com>
0 siblings, 0 replies; 3+ messages in thread
From: wcrowell @ 2020-04-03 15:02 UTC (permalink / raw)
To: pgsql-bugs
Tim,
No problem. Do you happen to know what release this will be fixed in?
Maybe 11.8?
Regards,
Bill Crowell
--
Sent from: https://www.postgresql-archive.org/PostgreSQL-bugs-f2117394.html
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2020-04-03 15:02 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2020-04-03 13:46 BUG #16340: lo_manage() crashs DB instance PG Bug reporting form <noreply@postgresql.org>
2020-04-03 14:40 ` Tom Lane <tgl@sss.pgh.pa.us>
2020-04-03 15:02 ` wcrowell <wcrowell@perforce.com>
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