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 (view raw or flat )
Thread:
2006-10-26 20:45:02 from Chris Campbell <chris(at)bignerdranch(dot)com>
2006-10-26 21:21:26 from Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
2006-10-26 22:11:59 from Chris Campbell <chris(at)bignerdranch(dot)com>
2006-10-26 22:29:11 from "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
2006-10-26 22:45:08 from Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
2006-10-26 23:23:12 from Alvaro Herrera <alvherre(at)commandprompt(dot)com>
2006-10-27 00:27:31 from Chris Campbell <chris(at)bignerdranch(dot)com>
2006-10-30 20:49:57 from "Simon Riggs" <simon(at)2ndquadrant(dot)com>
2007-02-14 03:19:15 from Bruce Momjian <bruce(at)momjian(dot)us>
2007-02-19 19:38:41 from "Simon Riggs" <simon(at)2ndquadrant(dot)com>
2007-02-19 22:29:40 from "Simon Riggs" <simon(at)2ndquadrant(dot)com>
2007-02-26 18:34:01 from Bruce Momjian <bruce(at)momjian(dot)us>
2007-02-26 19:01:24 from "Simon Riggs" <simon(at)2ndquadrant(dot)com>
2007-02-26 19:11:23 from Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
2007-02-26 19:19:49 from "Simon Riggs" <simon(at)2ndquadrant(dot)com>
2007-02-26 19:28:26 from Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
2007-02-26 19:31:49 from "Simon Riggs" <simon(at)2ndquadrant(dot)com>
2007-02-26 19:52:03 from Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
2007-02-26 20:05:07 from "Simon Riggs" <simon(at)2ndquadrant(dot)com>
2007-02-26 20:10:49 from Bruce Momjian <bruce(at)momjian(dot)us>
2007-02-26 20:15:43 from Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
2007-03-01 02:06:15 from Bruce Momjian <bruce(at)momjian(dot)us>
2007-03-01 05:45:54 from Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
2007-03-01 14:06:41 from Bruce Momjian <bruce(at)momjian(dot)us>
2007-03-01 19:17:20 from Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
2007-03-02 18:35:41 from Bruce Momjian <bruce(at)momjian(dot)us>
2007-03-02 18:51:32 from Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
2007-03-02 20:20:27 from Bruce Momjian <bruce(at)momjian(dot)us>
2007-03-02 20:55:05 from Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
2007-03-02 22:05:41 from Bruce Momjian <bruce(at)momjian(dot)us>
2007-03-02 22:37:33 from Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
2007-03-02 22:46:40 from Bruce Momjian <bruce(at)momjian(dot)us>
2007-03-02 23:38:54 from Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
2007-03-03 02:40:54 from Bruce Momjian <bruce(at)momjian(dot)us>
2007-03-03 02:43:54 from Bruce Momjian <bruce(at)momjian(dot)us>
2007-03-03 18:49:32 from Bruce Momjian <bruce(at)momjian(dot)us>
2006-11-21 04:40:15 from Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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. +
In response to
Responses
pgsql-hackers by date
Next :From: Alvaro HerreraDate: 2007-03-02 22:49:49Subject : Re: HOT - preliminary resultsPrevious :From : Bruno Wolff IIIDate : 2007-03-02 22:38:31Subject : Re: Is there a way to run heap_insert() AFTER ExecInsertIndexTuples() ?
pgsql-patches by date
Next :From: FAST PostgreSQLDate: 2007-03-02 23:13:10Subject : Re: [PATCHES] WIP Patch - Updateable CursorsPrevious :From : Tom LaneDate : 2007-03-02 22:37:33Subject : Re: [HACKERS] Deadlock with pg_dump?
