Re: Verifying variable names in pgbench - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Verifying variable names in pgbench
Date
Msg-id 603c8f071001041933g152066cct7941721f9a498978@mail.gmail.com
Whole thread Raw
In response to Re: Verifying variable names in pgbench  (Takahiro Itagaki <itagaki.takahiro@oss.ntt.co.jp>)
Responses Re: Verifying variable names in pgbench  (Takahiro Itagaki <itagaki.takahiro@oss.ntt.co.jp>)
List pgsql-hackers
On Mon, Jan 4, 2010 at 10:00 PM, Takahiro Itagaki
<itagaki.takahiro@oss.ntt.co.jp> wrote:
>
> Takahiro Itagaki <itagaki.takahiro@oss.ntt.co.jp> wrote:
>
>> We can remove the complexity if we give up showing the command (arg0)
>> in error messages. Shall we remove it? Simplified patch attached.
>
> Here is the proposal for the arg0 issue.
> I added "context" argument to putVariable(). The context is a command
> name for \setXXX commands, 'option' for -D option, or 'startup' for
> internal assignment in startup.

What is currently done for other, similar error messages?

...Robert


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pg_migrator issues
Next
From: Robert Haas
Date:
Subject: Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting