Re: message clarifications - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: message clarifications
Date
Msg-id 1270546232.24910.5701.camel@ebony
Whole thread Raw
In response to message clarifications  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: message clarifications  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On Sat, 2010-04-03 at 11:00 +0300, Peter Eisentraut wrote:
> The following messages from the postgres catalog either appear to be
> internal errors that should be marked differently, or they are in my
> estimation unintelligible to users and should be rephrased.

> #: storage/ipc/procarray.c:2224
> msgid "record known xact %u latestObservedXid %u"
> 
> 
> #: storage/ipc/procarray.c:2257
> msgid "recording unobserved xid %u (latestObservedXid %u)"
> 
> 
> #: storage/ipc/procarray.c:2379
> msgid "too many KnownAssignedXids"
> 
> 
> #: storage/ipc/standby.c:861
> msgid ""
> "snapshot of %u running transactions overflowed (lsn %X/%X oldest "
> "xid %u next xid %u)"
> 
> 
> #: storage/ipc/standby.c:868
> msgid ""
> "snapshot of %u running transaction ids (lsn %X/%X oldest xid %u "
> "next xid %u)"

These are all DEBUG messages. Can you explain "marked differently" so I
can do that for you?

-- Simon Riggs           www.2ndQuadrant.com



pgsql-hackers by date:

Previous
From: Takahiro Itagaki
Date:
Subject: Re: SELECT constant; takes 15x longer on 9.0?
Next
From: Heikki Linnakangas
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Check compulsory parameters in recovery.conf in standby_mode, per