Re: Re: [COMMITTERS] pgsql: Add support for matching wildcard server certificates to the new

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: [COMMITTERS] pgsql: Add support for matching wildcard server certificates to the new
Date: 2008-12-01 17:18:41
Message-ID: 92EED756-A454-4AD6-B7D0-80FE358388AC@hagander.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 1 dec 2008, at 18.10, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>> I could assign it to a variable, but won't the compiler just optimize
>> that away?
>
> Wouldn't count on that, particularly not if you are modifying other
> strings at the same time.
>
I'm not modifying them. But - point taken, will change.

Another q: given that we no longer need fnmatch(), should we remove it
from port, or leave it around in case we need it in the future? (it's
not like we can't get it back if we need it, but...)

/Magnus

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2008-12-01 17:28:32 Re: Re: [COMMITTERS] pgsql: Add support for matching wildcard server certificates to the new
Previous Message Heikki Linnakangas 2008-12-01 17:11:18 pgsql: Modify the new to_timestamp implementation so that

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-12-01 17:22:45 Re: New to_timestamp implementation is pretty strict
Previous Message Tom Lane 2008-12-01 17:10:15 Re: Re: [COMMITTERS] pgsql: Add support for matching wildcard server certificates to the new