From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, dinesh kumar <dineshkumar02(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal: multiple psql option -c |
Date: | 2015-08-28 21:01:44 |
Message-ID: | 55E0CC38.7010505@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 8/28/15 3:31 PM, David G. Johnston wrote:
> --psqlrc
> ; read the standard rc files
> --no-psqlrc ; do not read the standard rc files
>
> It belongs in a separate patch, though.
>
> In this patch -g should disable the reading of the standard rc files.
Agreed; I didn't realize -c disabled psqlrc.
> Yet another option could be added that allows the user to point to a
> different set of rc files. Its presence should not cause the
> include/exclude behavior to change. That way you can setup a psql
> wrapper function or alias that uses a different rc file while still
> having control over whether it is included or excluded. The problem
> here is exploding the logic in order to deal with both a system and a
> user rc file.
If we had a \i variation that didn't fail if the file wasn't readable
you could use that to pull a system psqlrc in from your custom one.
--
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 | Thomas Munro | 2015-08-28 21:03:17 | Re: NOTIFY in Background Worker |
Previous Message | Tom Lane | 2015-08-28 20:55:52 | Re: Function accepting array of complex type |