| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Undefined psql variables |
| Date: | 2017-04-02 20:57:00 |
| Message-ID: | alpine.DEB.2.20.1704022249001.11400@lancre |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I'm inclined to suggest that we should require all extensions beyond the
> boolean-literal case to be set up as a keyword followed by appropriate
> argument(s); that seems like it's enough to prevent syntax conflicts from
> future additions. So you could imagine
>
> \if defined varname
> \if sql boolean expression to send to server
> \if compare value operator value
I'm still thinking:-)
Independently of the my aethetical complaint against having a pretty
unusual keyword prefix syntax, how would you envision a \set assignment
variant? Would \if have a different expression syntax somehow?
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Venkata B Nagothi | 2017-04-02 22:19:20 | Re: [BUGS] Bug in Physical Replication Slots (at least 9.5)? |
| Previous Message | Fabien COELHO | 2017-04-02 20:33:06 | Re: Undefined psql variables |