From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Chris Campbell <chris(at)bignerdranch(dot)com>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: [HACKERS] Deadlock with pg_dump? |
Date: | 2007-03-02 22:46:40 |
Message-ID: | 200703022246.l22Mkeo10707@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
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
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2007-03-02 22:49:49 | Re: HOT - preliminary results |
Previous Message | Bruno Wolff III | 2007-03-02 22:38:31 | Re: Is there a way to run heap_insert() AFTER ExecInsertIndexTuples() ? |
From | Date | Subject | |
---|---|---|---|
Next Message | FAST PostgreSQL | 2007-03-02 23:13:10 | Re: [PATCHES] WIP Patch - Updateable Cursors |
Previous Message | Tom Lane | 2007-03-02 22:37:33 | Re: [HACKERS] Deadlock with pg_dump? |