Skip site navigation (1) Skip section navigation (2)

Re: Verifying variable names in pgbench

From: Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: Verifying variable names in pgbench
Date: 2010-01-05 03:00:51
Message-ID: 20100105120050.ABF0.52131E4D@oss.ntt.co.jp (view raw or flat)
Thread:
Lists: pgsql-hackers
Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)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.

Regards,
---
Takahiro Itagaki
NTT Open Source Software Center

Attachment: pgbench_verify_varname_20100105.patch
Description: application/octet-stream (4.7 KB)

In response to

Responses

pgsql-hackers by date

Next:From: John NaylorDate: 2010-01-05 03:14:40
Subject: Re: Does parallel make require guards against duplicate actions?
Previous:From: Tom LaneDate: 2010-01-05 02:58:58
Subject: Does parallel make require guards against duplicate actions?

Privacy Policy | About PostgreSQL
Copyright © 1996-2013 The PostgreSQL Global Development Group