Re: Wildcard usage enhancements in .pgpass

From: Alexey Klyukin <alexk(at)hintbits(dot)com>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Wildcard usage enhancements in .pgpass
Date: 2013-11-18 06:57:52
Message-ID: CAAS3tyKCzZm6iifFUWYOM-79QzRgRnCm8XVkQ20U6sPwLWridA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Martijn,

On Sun, Nov 17, 2013 at 7:56 PM, Martijn van Oosterhout
<kleptog(at)svana(dot)org>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 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.
>

fnmatch(3) looks like a good deal and I'd certainly consider it if we go
the road of matching regular expressions, although for simpler use cases
it's an overkill, since it forces us to do an extra pass over the string to
be matched and introduces some performance penalties of using a regexp
matching engine.

--
Regards,
Alexey Klyukin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Abhijit Menon-Sen 2013-11-18 07:29:52 Re: [PATCH] Use MAP_HUGETLB where supported (v3)
Previous Message Amit Kapila 2013-11-18 06:01:54 Re: Extra functionality to createuser