On Thu, 24 Nov 2011 11:14:38 -0500, Robert Haas wrote:
But if no
input, however misguided, should ever cause that symptom, then it's,
I
don't know what the terminology should be, say, a "severe error".
"System Error"?
--
nw
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To
On tor, 2011-11-24 at 11:14 -0500, Robert Haas wrote:
> So I would propose to steer clear of the word "internal", because the
> really scary errors typically are not internal to PostgreSQL at all.
> What I think we want to distinguish between is things that are
> PEBKAC/GIGO, and everything else.
On 24 November 2011 16:55, Alvaro Herrera wrote:
>
> Excerpts from Robert Haas's message of jue nov 24 13:14:38 -0300 2011:
>
>> What I think we want to distinguish between is things that are
>> PEBKAC/GIGO, and everything else. In other words, if a particular
>> error message can be caused by ty
Excerpts from Robert Haas's message of jue nov 24 13:14:38 -0300 2011:
> What I think we want to distinguish between is things that are
> PEBKAC/GIGO, and everything else. In other words, if a particular
> error message can be caused by typing something stupid, unexpected,
> erroneous, or whatev
On Wed, Nov 23, 2011 at 7:19 AM, Peter Geoghegan wrote:
> On 23 November 2011 02:49, Robert Haas wrote:
>> There is no sort of systematic labeling of error messages in the log
>> to enable the DBA to figure out that the first error message is likely
>> nothing more serious than an integrity const
On 23 November 2011 02:49, Robert Haas wrote:
> There is no sort of systematic labeling of error messages in the log
> to enable the DBA to figure out that the first error message is likely
> nothing more serious than an integrity constraint doing its bit to
> preserve data integrity, while the se
On Fri, Nov 18, 2011 at 3:52 PM, Tomas Vondra wrote:
>> 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
>>
"Tomas Vondra" writes:
> On 18 Listopad 2011, 20:38, Tigran Mkrtchyan wrote:
>> I think it's a bug to log with level ERROR absolute valid SQL
>> statement.
But it's *not* valid ... it failed.
> If you don't want to see those messages in the log, there are ways to do
> that correctly -
Has anybo
On Fri, Nov 18, 2011 at 14:31, Tigran Mkrtchyan
wrote:
>
> On Fri, Nov 18, 2011 at 9:52 PM, Tomas Vondra wrote:
> > Anyway this definitely is not a bug,
>
> Still not convinced.
You are unlikely to convince anyone here otherwise... Its works that
way by design.
> [...] I don't think you will
On Fri, Nov 18, 2011 at 9:52 PM, Tomas Vondra wrote:
> On 18 Listopad 2011, 20:38, Tigran Mkrtchyan wrote:
>> On Fri, Nov 18, 2011 at 6:52 PM, Tomas Vondra wrote:
>>> On 18 Listopad 2011, 17:42, Tigran Mkrtchyan wrote:
The following bug has been logged online:
Bug reference:
On 18 Listopad 2011, 20:38, Tigran Mkrtchyan wrote:
> On Fri, Nov 18, 2011 at 6:52 PM, Tomas Vondra wrote:
>> On 18 Listopad 2011, 17:42, Tigran Mkrtchyan wrote:
>>>
>>> The following bug has been logged online:
>>>
>>> Bug reference: 6300
>>> Logged by: Tigran Mkrtchyan
>>> Email ad
On Fri, Nov 18, 2011 at 6:52 PM, Tomas Vondra wrote:
> On 18 Listopad 2011, 17:42, Tigran Mkrtchyan wrote:
>>
>> The following bug has been logged online:
>>
>> Bug reference: 6300
>> Logged by: Tigran Mkrtchyan
>> Email address: tigran.mkrtch...@desy.de
>> PostgreSQL version: 9
On 18 Listopad 2011, 17:42, Tigran Mkrtchyan wrote:
>
> The following bug has been logged online:
>
> Bug reference: 6300
> Logged by: Tigran Mkrtchyan
> Email address: tigran.mkrtch...@desy.de
> PostgreSQL version: 9.0.4
> Operating system: Linux x86_64
> Description:d
The following bug has been logged online:
Bug reference: 6300
Logged by: Tigran Mkrtchyan
Email address: tigran.mkrtch...@desy.de
PostgreSQL version: 9.0.4
Operating system: Linux x86_64
Description:duplicate key value violates unique constraint
Details:
Hi,
our ap
14 matches
Mail list logo
