Re: [HACKERS] Deadlock with pg_dump?

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Tom Lane wrote:
>> Perhaps the best thing would be to define an additional ereport
>> auxiliary function, say errprintstmt(bool), that could set a flag
>> in the current elog stack entry to control suppression of STATEMENT.
>> This would mean you couldn't determine the behavior when using elog(),
>> but that's not supposed to be used for user-facing messages anyway.

> One idea I had was to set the high-bit of elevel to control whether we
> want to suppress statement logging, but I think errprintstmt() might be
> best. I don't understand the ereport stack well enough to add this
> functionality, though. What should I look for?

It wouldn't really be any different from errcode(), but if you want
I'll do it.

regards, tom lane