| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | dakotali kasap | 2006-10-27 08:58:21 | printing the query plan? |
| Previous Message | Zeugswetter Andreas ADI SD | 2006-10-27 08:54:03 | Re: New CRC algorithm: Slicing by 8 |