| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | message clarifications |
| Date: | 2010-04-03 08:00:17 |
| Message-ID: | 1270281617.30101.6.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
#: commands/async.c:1424
msgid "pg_notify queue is %.0f%% full"
#: 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)"
Help please.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2010-04-03 10:12:55 | Re: message clarifications |
| Previous Message | Andrew Dunstan | 2010-04-03 02:10:26 | Re: pgindent bizarreness |