| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PATCH: pgbench allow '=' in \set |
| Date: | 2015-05-07 18:57:08 |
| Message-ID: | alpine.DEB.2.10.1505072053480.20788@sto |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Would "colon-equal" be more acceptable - like in pl/pgsql?
Hmmm... I would tend to think that is even clearer as a separator than a
mere "=". Too much Pascal in my youth? :-)
Although ":" means beginning of variable name in pgbench, I would not
think that it is an issue because = is not a valid variable name.
> Even if "=" becomes a valid operator I would have to think it is a binary
> operator and so its position at the start of an expression would still be
> unambiguous as to whether it is cosmetic or functional.
That is also my conclusion.
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2015-05-07 19:00:49 | Re: Disabling trust/ident authentication configure option |
| Previous Message | Fabien COELHO | 2015-05-07 18:53:06 | Re: PATCH: pgbench allow '=' in \set |