| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Verifying variable names in pgbench |
| Date: | 2010-01-05 03:51:10 |
| Message-ID: | 603c8f071001041951r64a3a9as9672435b3a00efaf@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jan 4, 2010 at 10:44 PM, Takahiro Itagaki
<itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
>> What is currently done for other, similar error messages?
>
> Current error messages are:
> for commands: "<context>: out of memory"
> for others : "Couldn't allocate memory for variable"
>
> The new message is: "<context>: out of memory for variable '<name>'"
OK, I see. I think this is reasonable, then.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-01-05 03:51:34 | Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting |
| Previous Message | Takahiro Itagaki | 2010-01-05 03:44:38 | Re: Verifying variable names in pgbench |