Skip site navigation (1) Skip section navigation (2)

Re: Deadlock with pg_dump?

From: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
To: "Csaba Nagy" <nagy(at)ecircle-ag(dot)com>
Cc: "Albe Laurenz" <all(at)adv(dot)magwien(dot)gv(dot)at>, "Chris Campbell" <chris(at)bignerdranch(dot)com>, "postgres hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Deadlock with pg_dump?
Date: 2006-10-27 08:54:31
Message-ID: 4155.24.211.165.134.1161939271.squirrel@www.dunslane.net (view raw or flat)
Thread:
Lists: pgsql-hackers
Csaba Nagy wrote:
> On Fri, 2006-10-27 at 09:23, Albe Laurenz wrote:
>> > [ Memo to hackers: why is it that log_min_error_statement = error
>> > isn't the default? ]
>>
>> To avoid spamming the logs with every failed SQL statement?
>
> And it would be hurting applications where query failure is taken as a
> valid path (as inserting first and update if failing)...
>

Both of these are arguments in favor of being able to alter the level,
which would still exist. They are not good arguments for not having error
as the default level.

cheers

andrew


In response to

pgsql-hackers by date

Next:From: dakotali kasapDate: 2006-10-27 08:58:21
Subject: printing the query plan?
Previous:From: Zeugswetter Andreas ADI SDDate: 2006-10-27 08:54:03
Subject: Re: New CRC algorithm: Slicing by 8

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group