Re: [HACKERS] Wildcard usage enhancements in .pgpass

2013-12-06 Thread Peter Eisentraut
On 11/17/13, 1:56 PM, Martijn van Oosterhout wrote: > Looks interesting, though I wonder if you could use fnmatch(3) here. Or > woud that match more than you expect? For example, it would allow > 'foo*bar' to match 'foo.bar' which your code doesn't. The question is whether you'd want that. We ha

Re: [HACKERS] Wildcard usage enhancements in .pgpass

2013-11-19 Thread Robert Haas
On Mon, Nov 18, 2013 at 1:57 AM, Alexey Klyukin wrote: > Hi Martijn, > > On Sun, Nov 17, 2013 at 7:56 PM, Martijn van Oosterhout > wrote: >> >> On Sat, Nov 16, 2013 at 09:26:33PM +0100, Alexey Klyukin wrote: >> > Hi, >> > >> > Attached is the patch that improves usage of '*' wildcard in .pgpass,

Re: [HACKERS] Wildcard usage enhancements in .pgpass

2013-11-17 Thread Alexey Klyukin
Hi Martijn, On Sun, Nov 17, 2013 at 7:56 PM, Martijn van Oosterhout wrote: > On Sat, Nov 16, 2013 at 09:26:33PM +0100, Alexey Klyukin wrote: > > Hi, > > > > Attached is the patch that improves usage of '*' wildcard in .pgpass, > > particularly in the host part. The use case is below. > > Looks in

Re: [HACKERS] Wildcard usage enhancements in .pgpass

2013-11-17 Thread Martijn van Oosterhout
On Sat, Nov 16, 2013 at 09:26:33PM +0100, Alexey Klyukin wrote: > Hi, > > Attached is the patch that improves usage of '*' wildcard in .pgpass, > particularly in the host part. The use case is below. Looks interesting, though I wonder if you could use fnmatch(3) here. Or woud that match more than