On Fri, Jan 21, 2011 at 11:47 AM, Tom Lane wrote:
> Magnus Hagander writes:
>> On Fri, Jan 21, 2011 at 16:40, Robert Haas wrote:
>>> So... is there centralized structure which contains the info you're
>>> thinking of exposing?
>
>> No, not today.
>
> I think that most of the info Magnus suggeste
Magnus Hagander writes:
> On Fri, Jan 21, 2011 at 16:40, Robert Haas wrote:
>> So... is there centralized structure which contains the info you're
>> thinking of exposing?
> No, not today.
I think that most of the info Magnus suggested isn't stored at all,
anywhere, at the moment; much less sto
On Fri, Jan 21, 2011 at 10:43 AM, Magnus Hagander wrote:
> On Fri, Jan 21, 2011 at 16:40, Robert Haas wrote:
>> On Fri, Jan 21, 2011 at 10:34 AM, Magnus Hagander
>> wrote:
>>> Um, none of the fields I've suggested so far was "connection string".
>>> In fact, that would be Pretty Darn Hard witho
On Fri, Jan 21, 2011 at 16:40, Robert Haas wrote:
> On Fri, Jan 21, 2011 at 10:34 AM, Magnus Hagander 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
On Fri, Jan 21, 2011 at 10:34 AM, Magnus Hagander 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 structur
On Fri, Jan 21, 2011 at 16:32, Robert Haas wrote:
> On Fri, Jan 21, 2011 at 10:14 AM, Magnus Hagander wrote:
>> On Fri, Jan 21, 2011 at 15:51, Tom Lane wrote:
>>> Magnus Hagander writes:
I came across a case this week where I wanted to be able to determine
more detailed auth informati
On Fri, Jan 21, 2011 at 10:14 AM, Magnus Hagander wrote:
> On Fri, Jan 21, 2011 at 15:51, Tom Lane wrote:
>> Magnus Hagander writes:
>>> I came across a case this week where I wanted to be able to determine
>>> more detailed auth information on already logged in sessions - not
>>> from the clien
On Fri, Jan 21, 2011 at 15:51, Tom Lane wrote:
> Magnus Hagander writes:
>> I came across a case this week where I wanted to be able to determine
>> more detailed auth information on already logged in sessions - not
>> from the client, but from the server. In this specific case, I wanted
>> to ex
Magnus Hagander writes:
> I came across a case this week where I wanted to be able to determine
> more detailed auth information on already logged in sessions - not
> from the client, but from the server. In this specific case, I wanted
> to examine the "is ssl" flag on the connection. But I can s
I came across a case this week where I wanted to be able to determine
more detailed auth information on already logged in sessions - not
from the client, but from the server. In this specific case, I wanted
to examine the "is ssl" flag on the connection. But I can see other
things being interesting
10 matches
Mail list logo
