| Lists: | pgsql-hackers |
|---|
| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | separate initdb -A options for local and host |
| Date: | 2011-11-25 23:20:11 |
| Message-ID: | 1322263211.2104.7.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-hackers |
I think it would be useful to have separate initdb -A options for local
and host entries. In 9.1, we went out of our way to separate the "peer"
and "ident" methods, but we have moved the confusion into the initdb -A
option, where "ident" sometimes means "peer", and "peer" sometimes means
"ident". Moreover, having separate options would allow what I think
would be a far more common use case, namely having local "peer" and host
something other than "ident", such as "md5".
I'm thinking, we could keep the existing -A option, but add long options
such as --auth-local and --auth-host, to specify more detail.
| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: separate initdb -A options for local and host |
| Date: | 2012-01-14 22:18:51 |
| Message-ID: | 1326579531.31492.20.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-hackers |
On lör, 2011-11-26 at 01:20 +0200, Peter Eisentraut wrote:
> I think it would be useful to have separate initdb -A options for local
> and host entries. In 9.1, we went out of our way to separate the "peer"
> and "ident" methods, but we have moved the confusion into the initdb -A
> option, where "ident" sometimes means "peer", and "peer" sometimes means
> "ident". Moreover, having separate options would allow what I think
> would be a far more common use case, namely having local "peer" and host
> something other than "ident", such as "md5".
>
> I'm thinking, we could keep the existing -A option, but add long options
> such as --auth-local and --auth-host, to specify more detail.
Here is a patch that implements exactly that.
| Attachment | Content-Type | Size |
|---|---|---|
| initdb-auth-options.patch | text/x-patch | 10.1 KB |
| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: separate initdb -A options for local and host |
| Date: | 2012-01-16 02:26:25 |
| Message-ID: | CA+Tgmoa5ifQfW7EchZCk1XSRgJ2Uh2P6Zf5qP9KJ2NubYi7iXQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-hackers |
On Sat, Jan 14, 2012 at 5:18 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On lör, 2011-11-26 at 01:20 +0200, Peter Eisentraut wrote:
>> I think it would be useful to have separate initdb -A options for local
>> and host entries. In 9.1, we went out of our way to separate the "peer"
>> and "ident" methods, but we have moved the confusion into the initdb -A
>> option, where "ident" sometimes means "peer", and "peer" sometimes means
>> "ident". Moreover, having separate options would allow what I think
>> would be a far more common use case, namely having local "peer" and host
>> something other than "ident", such as "md5".
>>
>> I'm thinking, we could keep the existing -A option, but add long options
>> such as --auth-local and --auth-host, to specify more detail.
>
> Here is a patch that implements exactly that.
I reviewed this patch. It looks OK to me.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company