Tom Lane wrote:
> 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.
If you would just add the infrastructure I can add the LOG part.
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
+ If your life is a hard drive, Christ can be your backup. +
In response to
pgsql-hackers by date
|Next:||From: Alvaro Herrera||Date: 2007-03-02 22:49:49|
|Subject: Re: HOT - preliminary results|
|Previous:||From: Bruno Wolff III||Date: 2007-03-02 22:38:31|
|Subject: Re: Is there a way to run heap_insert() AFTER ExecInsertIndexTuples() ?|
pgsql-patches by date
|Next:||From: FAST PostgreSQL||Date: 2007-03-02 23:13:10|
|Subject: Re: [PATCHES] WIP Patch - Updateable Cursors|
|Previous:||From: Tom Lane||Date: 2007-03-02 22:37:33|
|Subject: Re: [HACKERS] Deadlock with pg_dump? |