On Fri, Nov 18, 2011 at 6:52 PM, Tomas Vondra <tv@fuzzy.cz> wrote:
> On 18 Listopad 2011, 17:42, Tigran Mkrtchyan wrote:
>>
>> The following bug has been logged online:
>>
>> Bug reference: =C2=A0 =C2=A0 =C2=A06300
>> Logged by: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Tigran Mkrtchyan
>> Email address: =C2=A0 =C2=A0 =C2=A0tigran.mkrtchyan@desy.de
>> PostgreSQL version: 9.0.4
>> Operating system: =C2=A0 Linux x86_64
>> Description: =C2=A0 =C2=A0 =C2=A0 =C2=A0duplicate key value violates uni=
que constraint
>> Details:
>>
>> Hi,
>>
>> our application uses PostgreSQL as a backend and heavily
>> relays on transactions. We never check constrains in our application as =
DB
>> does is better than we can an in an atomic way. This works very-very goo=
d!
>> Nevertheless the logfiles are full of 'duplicate key value violates uniq=
ue
>> constraint'. I have two questions:
>
> If it's a question, then why have you submitted it as a bug?
Then let me re-phrase it:
I think it's a bug to log with level ERROR absolute valid SQL
statement. You have error code returned to the client to handle it. If
I want to log statements then I can turned that on. This is client
appication debuggging and to error handling.
Regards,
Tigran.
>This is not a
> bug, it's correct and expected behavior - please, repost the questions to
> the appropriate place, e.g. pgsql-general mailing list.
>
> Tomas
>
>>
>> 1. why it logged with ERROR level as it clients application behavior.
>>
>> 2. is there a way to suppress it or could you add a way to suppress it.
>>
>>
>> Thanks a lot,
>> =C2=A0 =C2=A0Tigran.
>>
>> --
>> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-bugs
>>
>
>
>