Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] keeping track of connections

From: dg(at)illustra(dot)com (David Gould)
To: brett(at)work(dot)chicken(dot)org (Brett McCormick)
Cc: maillist(at)candle(dot)pha(dot)pa(dot)us, pgsql-hackers(at)hub(dot)org
Subject: Re: [HACKERS] keeping track of connections
Date: 1998-06-03 08:05:17
Message-ID: 9806030805.AA01067@hawk.illustra.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Brett M writes: 
> On Wed, 3 June 1998, at 00:11:01, Bruce Momjian wrote:
> 
> > Good question.  Postmaster does not have access to the system tables, so
> > it can't access them.  You could add a debug option to show it in the
> > server logs, or add it to the -d2 debug option that already shows SQL
> > statements.
> 
> How about something like this: a pool of shared memory where this
> information is stored, and then a view which calls a set of functions
> to return the information from the shared memory?
> 
> Apache does something similar.

I am curious, what is it you are trying to accomplish with this? Are you 
trying to build a persistant log that you can query later for billing
or load management/capacity planning information? Are you trying to monitor
login attempts for security auditing? Are you trying to catch logins in
real time for some sort of middleware integration?

Here we are discussion solutions, but I don't even know what the problem
is. So, please describe what is needed in terms of requirements/functionality.

Thanks

-dg


David Gould            dg(at)illustra(dot)com           510.628.3783 or 510.305.9468 
Informix Software  (No, really)         300 Lakeside Drive  Oakland, CA 94612
"Don't worry about people stealing your ideas.  If your ideas are any
 good, you'll have to ram them down people's throats." -- Howard Aiken

In response to

Responses

pgsql-hackers by date

Next:From: Steve LogueDate: 1998-06-03 08:35:10
Subject: NEW POSTGRESQL LOGOS
Previous:From: David GouldDate: 1998-06-03 06:26:06
Subject: Re: [HACKERS] regular expressions from hell

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group