| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: message clarifications |
| Date: | 2010-04-04 20:27:50 |
| Message-ID: | 1270412870.7026.3.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On lör, 2010-04-03 at 11:13 -0400, Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > 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"
>
> This one is probably my responsibility (the others all look like Simon's
> code). What do you not like about it, exactly? Perhaps it should be
> "NOTIFY queue is x% full"?
Yeah, that plus some hints maybe. "pg_notify" had me confused
initially, since it looks like a system catalog table name.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2010-04-04 20:45:37 | Nice hint on table aliasing! |
| Previous Message | Josh Berkus | 2010-04-04 19:29:38 | Wierd quirk of HS/SR, probably not fixable |