| From: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
|---|---|
| To: | "Fabien COELHO" <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>,"PostgreSQL Developers" <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: Variable substitution in psql backtick expansion |
| Date: | 2017-04-02 13:31:02 |
| Message-ID: | 0c41e787-067f-4413-82ef-445772539d96@manitou-mail.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Fabien COELHO wrote:
> Note that this is already available indirectly, as show in the
> documentation.
>
> SELECT some-boolean-expression AS okay \gset
> \if :okay
> \echo boolean expression was true
> \else
> \echo boolean expression was false
> \endif
Yes, the question was whether we leave it as that for v10,
or if it's worth a last-minute improvement for usability,
assuming it's doable, similarly to what $subject does to backtick
expansion for external evaluation.
Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2017-04-02 14:38:16 | Re: Variable substitution in psql backtick expansion |
| Previous Message | Konstantin Knizhnik | 2017-04-02 13:30:24 | FDW and parallel execution |