So I'll admit to using it, only in "toy" setups...

I use it with trust and ident, on local connections though, not password....

I try to keep my laptops clean of mysqld, and I use PG.  And only on my
laptop/PC,  I make a database for every user...  And every "app" get's a
userid, and a schema....    Every user get's passwordless access to their
database.  And the "userid" associates the app, and the defaults that get
used on their connections.

So, I think it's "neat", but wouldn't be put out if it was removed ...

On Tue, Mar 11, 2014 at 9:47 AM, Magnus Hagander <>wrote:

> On Tue, Mar 11, 2014 at 2:40 PM, Tom Lane <> wrote:
>> Magnus Hagander <> writes:
>> > On Sun, Mar 9, 2014 at 9:00 PM, Thom Brown <> wrote:
>> >> It will be 12 years this year since this "temporary measure" was
>> >> added.  I'm just wondering, is there any "complete solution" that
>> >> anyone had in mind yet?  Or should this just be deprecated?
>> > I'd say +1 to remove it. That would also make it possible to get id of
>> > "password" authentication...
>> If we remove it without providing a substitute feature, people who are
>> using it will rightly complain.
>> Are you claiming there are no users, and if so, on what evidence?
> I am claiming that I don't think anybody is using that, yes.
> Based on the fact that I have *never* come across it on any system I've
> come across since, well, forever. Except once I think, many years ago, when
> someone had enabled it by mistake and needed my help to remove it...
> But we should absolutely deprecate it first in that place. Preferrably
> visibly (e.g. with a log message when people use it). That could at least
> get those people who use it to let us know they do, to that way figure out
> if they do - and can de-deprecate it.
> Or if someone wants to fix it properly of course :)
> --
>  Magnus Hagander
>  Me:
>  Work:

Aidan Van Dyk                                             Create like a god,                                       command like a king,                                   work like a

Reply via email to