| From: | David Christensen <david(at)endpoint(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, gabrielle <gorthx(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Mark Wong <markwkm(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Explicit psqlrc |
| Date: | 2010-07-20 19:36:39 |
| Message-ID: | F56030FD-F193-4A29-95F1-E39DF5379952@endpoint.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Jul 20, 2010, at 2:18 PM, Alvaro Herrera wrote:
> Excerpts from Robert Haas's message of mar jul 20 11:48:29 -0400 2010:
>
>>> That seems sub-optimal; I can see people wanting to use this feature to do something like:
>>>
>>> psql -c 'set work_mem = blah' -f script.sql
>>>
>>> and then being surprised when it works differently than just `psql -f script.sql`.
>>
>> I agree... but then they might also be surprised if psql -c
>> 'something' works differently from psql -c 'something' -f /dev/null
>
> I think we should just make sure -X works, and have .psqlrc be read when
> it's not specified regardless of -f and -c switches.
>
> Otherwise it's just plain confusing.
+1.
Regards,
David
--
David Christensen
End Point Corporation
david(at)endpoint(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2010-07-20 20:22:31 | Re: managing git disk space usage |
| Previous Message | Peter Eisentraut | 2010-07-20 19:34:00 | Re: standard_conforming_strings |