Re: replace all with * in pg_hba.conf

From: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Postgresql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: replace all with * in pg_hba.conf
Date: 2003-12-19 15:28:04
Message-ID: 20031219112726.C3016@ganymede.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Fri, 19 Dec 2003, Tom Lane wrote:

> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> > The minimal disturbance change might be to teach the parser to
> > distinguish between a quoted 'all' and an unquoted 'all', and forget the
> > '*' idea.
>
> Probably we ought to go with that, on backwards-compatibility grounds.

why not do both, but deprecate the use of all in the docs? say with an
eventual goal of removing the use of all altogether in 2 releases?

----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2003-12-19 15:33:11 distinguish between all and "all" in pg_hba.conf
Previous Message Tom Lane 2003-12-19 15:19:30 Re: How can I return a NULL value from a function?

Browse pgsql-patches by date

  From Date Subject
Next Message Andrew Dunstan 2003-12-19 15:33:11 distinguish between all and "all" in pg_hba.conf
Previous Message Peter Eisentraut 2003-12-19 14:23:48 Re: [GENERAL] restore error - language "plperlu" is not trusted