| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Phil Sorber <phil(at)omniti(dot)com>, Erik Rijkers <er(at)xs4all(dot)nl>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal - assign result of query to psql variable |
| Date: | 2013-02-03 19:34:24 |
| Message-ID: | CAFj8pRBctV3imQ4KM1KVqK1BnVF1_=djLHPY0cMNMsXCqH8a7A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2013/2/3 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
>> now missing variables is replaced by variable's name. We can implement
>> some pset option - some like define what do with missing variable
>
>> \pset missing_variable (use_name | use_null | error )
>
> No, it isn't "replaced by variable's name". What actually happens is we
> don't attempt a replacement unless the string after the colon matches an
> existing variable. Tampering with that seems dangerous and foolish.
some other ideas?
do you think so full NULL support has sense?
Regards
Pavel
>
> regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2013-02-03 19:46:39 | Re: PATCH: Split stats file per database WAS: autovacuum stress-testing our system |
| Previous Message | Tom Lane | 2013-02-03 19:02:27 | Re: proposal - assign result of query to psql variable |