Re: message clarifications

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: message clarifications
Date: 2010-04-06 09:30:32
Message-ID: 1270546232.24910.5701.camel@ebony
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2010-04-06 09:31:04 Re: Remaining Streaming Replication Open Items
Previous Message Simon Riggs 2010-04-06 09:22:03 Hot Standby: Startup at shutdown checkpoint