| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | "Shulgin, Oleksandr" <oleksandr(dot)shulgin(at)zalando(dot)de> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: psql - better support pipe line |
| Date: | 2015-08-29 16:07:52 |
| Message-ID: | 55E1D8D8.2040601@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 8/29/15 8:10 AM, Shulgin, Oleksandr wrote:
> The other issue is there's no way to capture \conninfo inside of
> psql and do something with it. If instead this was exposed as a
> variable, you could handle it in SQL if you wanted to.
>
>
> Yeah, I forgot about the variable proposal, that would be a more useful
> way to expose it for sure.
Right. My only other point is it would be nice if what we exposed there
could be easily parsed in SQL. But as I said, having *anything* would be
an improvement.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2015-08-29 16:11:36 | Re: to_json(NULL) should to return JSON null instead NULL |
| Previous Message | Jim Nasby | 2015-08-29 16:06:05 | Re: Fwd: Core dump with nested CREATE TEMP TABLE |