Re: Incomplete Explain for delete - Mailing list pgsql-bugs

From David Gould
Subject Re: Incomplete Explain for delete
Date
Msg-id 20150622153256.4ba1c6ce@engels
Whole thread Raw
In response to Re: Incomplete Explain for delete  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: Incomplete Explain for delete
List pgsql-bugs
On Mon, 22 Jun 2015 12:41:28 -0400
"David G. Johnston" <david.g.johnston@gmail.com> wrote:

> =E2=80=8BExcept that the query inside the trigger is known to system - th=
e fact it
> is wrapped in a trigger is an implementation detail that could, in theory,
> be bypassed in order to facilitate a more meaningful explain output.

Unless triggers are prohibited from using dynamic sql, the query really
cannot be known to the system.

-dg



--=20
David Gould              510 282 0869         daveg@sonic.net
If simplicity worked, the world would be overrun with insects.

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #13459: Replaying WAL logs can hang on startup
Next
From: socketpair@gmail.com
Date:
Subject: BUG #13462: Impossible to use COPY FORMAT BINARY in chunks through libpq