Horton
Menu

Re: Explicit psqlrc

David Christensen <david@endpoint.com>

View thread
From: David Christensen <david@endpoint.com>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Robert Haas <robertmhaas@gmail.com>, gabrielle <gorthx@gmail.com>, Stephen Frost <sfrost@snowman.net>, Simon Riggs <simon@2ndquadrant.com>, Mark Wong <markwkm@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2010-07-20T19:36:39Z
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@endpoint.com