Re: [HACKERS] .ini support for .pgpass

2011-04-07 Thread Fujii Masao
On Thu, Apr 7, 2011 at 2:38 AM, Peter Eisentraut wrote: >> #-comments seem like a fine idea. > > But it would have to be the user that would put the comment in there, > since we can't really install a default file. What about preparing something like pgpass.sample and installing it into $PREFIX/s

Re: [HACKERS] .ini support for .pgpass

2011-04-06 Thread Peter Eisentraut
On ons, 2011-04-06 at 09:47 -0400, Tom Lane wrote: > Marko Kreen writes: > > On Wed, Apr 6, 2011 at 9:55 AM, Joshua D. Drake > > wrote: > >> 1. More understandable .pgpass format. Yes, I understand our standard > >> format, most people won't. Like JoshB said, hard to debug. > > > How about allo

Re: [HACKERS] .ini support for .pgpass

2011-04-06 Thread Joshua D. Drake
On Wed, 2011-04-06 at 09:10 +0200, Martijn van Oosterhout wrote: > On Tue, Apr 05, 2011 at 11:55:04PM -0700, Joshua D. Drake wrote: > > I want to achieve two things: > > > > 1. More understandable .pgpass format. Yes, I understand our standard > > format, most people won't. Like JoshB said, hard t

Re: [HACKERS] .ini support for .pgpass

2011-04-06 Thread Tom Lane
Marko Kreen writes: > On Wed, Apr 6, 2011 at 9:55 AM, Joshua D. Drake > wrote: >> 1. More understandable .pgpass format. Yes, I understand our standard >> format, most people won't. Like JoshB said, hard to debug. > How about allowing '#'-comments there and putting field > list into all templat

Re: [HACKERS] .ini support for .pgpass

2011-04-06 Thread Marko Kreen
On Wed, Apr 6, 2011 at 9:55 AM, Joshua D. Drake wrote: > I want to achieve two things: > > 1. More understandable .pgpass format. Yes, I understand our standard > format, most people won't. Like JoshB said, hard to debug. How about allowing '#'-comments there and putting field list into all templ

Re: [HACKERS] .ini support for .pgpass

2011-04-06 Thread Martijn van Oosterhout
On Tue, Apr 05, 2011 at 11:55:04PM -0700, Joshua D. Drake wrote: > I want to achieve two things: > > 1. More understandable .pgpass format. Yes, I understand our standard > format, most people won't. Like JoshB said, hard to debug. This I understand. > 2. psql foo, gets me into foo. A macro for

Re: [HACKERS] .ini support for .pgpass

2011-04-05 Thread Joshua D. Drake
On Wed, 2011-04-06 at 07:47 +0300, Peter Eisentraut wrote: > On tis, 2011-04-05 at 16:04 -0700, Joshua D. Drake wrote: > > Well any libpq app but yes. I actually wonder as to the legitmacy of > > having both a pgpass and a pg_service. Why not just one of them? > > So you can keep passwords in a sa

Re: [HACKERS] .ini support for .pgpass

2011-04-05 Thread Peter Eisentraut
On tis, 2011-04-05 at 16:04 -0700, Joshua D. Drake wrote: > Well any libpq app but yes. I actually wonder as to the legitmacy of > having both a pgpass and a pg_service. Why not just one of them? So you can keep passwords in a safer place (= less permissions) than the rest of the connection inform

Re: [HACKERS] .ini support for .pgpass

2011-04-05 Thread Joshua D. Drake
On Tue, 2011-04-05 at 18:52 -0400, Aidan Van Dyk wrote: > On Tue, Apr 5, 2011 at 6:34 PM, Joshua D. Drake > wrote: > > > Bare, useful, but not really friendly nor flexible. I would love to be > > able to do this: > > > [ecom] > > hostname= > > port= > > database= > > username= > > password= >

Re: [HACKERS] .ini support for .pgpass

2011-04-05 Thread Aidan Van Dyk
On Tue, Apr 5, 2011 at 6:34 PM, Joshua D. Drake wrote: > Bare, useful, but not really friendly nor flexible. I would love to be > able to do this: > [ecom] > hostname= > port= > database= > username= > password= That looks a lot like a pg_service file. > psql ecom > > boom, I am in. > > Though

Re: [HACKERS] .ini support for .pgpass

2011-04-05 Thread Joshua D. Drake
On Tue, 2011-04-05 at 15:38 -0700, David E. Wheeler wrote: > On Apr 5, 2011, at 3:34 PM, Joshua D. Drake wrote: > > > boom, I am in. > > > > Thoughts? > > boom, you have patch? I'll write it, if I am not going to be tied up for months arguing about it :P. Thus, I wanted to see if the community

Re: [HACKERS] .ini support for .pgpass

2011-04-05 Thread David E. Wheeler
On Apr 5, 2011, at 3:34 PM, Joshua D. Drake wrote: > boom, I am in. > > Thoughts? boom, you have patch? David -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] .ini support for .pgpass

2011-04-05 Thread Josh Berkus
On 4/5/11 3:34 PM, Joshua D. Drake wrote: > Bare, useful, but not really friendly nor flexible. I would love to be > able to do this: I'll second that I help people troubleshoot a lot of .pgpass files where the basic issue is getting the fields out of order. -- Josh Berkus PostgreSQL Experts In

[HACKERS] .ini support for .pgpass

2011-04-05 Thread Joshua D. Drake
The current structure of .pgpass is: hostname:port:database:username:password Bare, useful, but not really friendly nor flexible. I would love to be able to do this: If no ini block: hostname:port:database:username:password else: [ecom] hostname= port= database= username= password= [drupal