| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: message clarifications |
| Date: | 2010-04-03 19:02:58 |
| Message-ID: | 4211199737690713170@unknownmsgid |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Apr 3, 2010, at 11:13 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 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"?
I think maybe the question is why the user should care, or what they
are expected to do about it?
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joachim Wieland | 2010-04-03 19:35:14 | Re: message clarifications |
| Previous Message | Boszormenyi Zoltan | 2010-04-03 16:22:39 | ECPG doesn't delete its output file in case of an error |