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

Re: [HACKERS] keeping track of connections

From: Hal Snyder <hal(at)enteract(dot)com>
To: pgsql-hackers(at)hub(dot)org
Subject: Re: [HACKERS] keeping track of connections
Date: 1998-06-03 14:20:30
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
> Date: Wed, 3 Jun 1998 02:37:58 -0700 (PDT)
> From: Brett McCormick <brett(at)work(dot)chicken(dot)org>
> Cc: maillist(at)candle(dot)pha(dot)pa(dot)us, pgsql-hackers(at)hub(dot)org
> Sender: owner-pgsql-hackers(at)hub(dot)org

> On Wed, 3 June 1998, at 01:05:17, David Gould wrote:
> > 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?
> The problem is that when I do a process listing for the postgres user,
> I see many backends.  There's no (convenient) way to see what those
> backends are doing, what db they're connected to or the remote
> host/postgres user.
> My required functionality is this: a list of all backends and
> connection details.  IP, queries issued, listens/notifications
> requested/served, bytes transfered, postgres user, db, current query,
> client version, etcetcetc.

Can backend monitoring be compatible with one or more extant
monitoring techniques?

1. syslog
2. HTML (like Apache's real time status)

In response to


pgsql-hackers by date

Next:From: Thomas G. LockhartDate: 1998-06-03 14:24:17
Subject: Re: [PATCHES] Postgres-6.3.2 locale patch
Previous:From: andreDate: 1998-06-03 14:15:31
Subject: Buffer leak?

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