From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: More detailed auth info |
Date: | 2011-01-21 15:54:09 |
Message-ID: | AANLkTikYsARp-rHBopany=VqjNBkCqJanYcwUXfUGimw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jan 21, 2011 at 10:43 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> On Fri, Jan 21, 2011 at 16:40, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> On Fri, Jan 21, 2011 at 10:34 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>>> Um, none of the fields I've suggested so far was "connection string".
>>> In fact, that would be Pretty Darn Hard without modifying the client
>>> to actually *send* the connection string. Which id doesn't.
>>
>> So... is there centralized structure which contains the info you're
>> thinking of exposing?
>
> No, not today. That's what would have to be created. (And before you
> or somebody says something, no, it's not on the CF, so this is likely
> a 9.2 feature unless that structure thingy turns out to be a lot
> *less* code than I think it will)
Well, unlike Tom, I don't object to the basic idea, but I reserve the
right to object in detail. :-)
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-01-21 15:57:23 | Re: review: FDW API |
Previous Message | Robert Haas | 2011-01-21 15:53:11 | Re: Sync Rep for 2011CF1 |