| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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-25 14:59:05 |
| Message-ID: | 55DC82B9.50108@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 8/24/15 3:04 PM, Pavel Stehule wrote:
> (1) there is no reason to believe that the db name and only the db name
> is needed to do another connection; what about port, host, user, etc?
>
>
> I have to agree - the possibilities is much more than database name - so
> one option is not good idea.
What I've had problems with is trying to correlate psql specified
connection attributes with things like DBI. It would be nice if there
was a way to get a fully formed connection URI for the current connection.
--
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 | Stephen Frost | 2015-08-25 15:17:09 | Re: CREATE POLICY and RETURNING |
| Previous Message | Stephen Frost | 2015-08-25 14:28:36 | Re: Commitfest remaining "Needs Review" items |