>
> > that. Having made that constraint, I see 3 contexts:
> >
> > 1) Server events. E.g.:
> > 2) User sessions.
> > 3) Transactions.
> >
>
> how about 3 different logs? pg_server.log, pg_sessions.log, pg_trans.log or
> something along those lines.. that way you could parse each file as they woul
> hi..
>
> > that. Having made that constraint, I see 3 contexts:
> >
> > 1) Server events. E.g.:
> > 2) User sessions.
> > 3) Transactions.
> >
>
> how about 3 different logs? pg_server.log, pg_sessions.log, pg_trans.log or
> something along those lines.. that way you could parse each file as
hi..
> that. Having made that constraint, I see 3 contexts:
>
> 1) Server events. E.g.:
> 2) User sessions.
> 3) Transactions.
>
how about 3 different logs? pg_server.log, pg_sessions.log, pg_trans.log or
something along those lines.. that way you could parse each file as they would
each have a
OK, It looks like there's at least some interest in having a
true logging facility for the PostgreSQL backend. I've
researched the source code and feel fairly certain that I
can provide a patchset that would provide information useful
to an administrator without having an unfortunate impact on
rel
Bruce Momjian wrote:
> > like logging to be up to modern-day quality expectations (e.g. filterable,
>routable, and securable) and to record not only basic session info, but statistical
>info to assist in tuning.
> >
> > So, returning to my own question. Is any such presently available that I'm
At 15:43 +0200 on 12/10/1999, Oleg Bartunov wrote:
> Cool ! Then we could use standard log-analyzers to produce
> any usage statistics.
Things will have to be considered before this can be done. The main problem
is that there is no way you can delimit a query and be sure the delimiter
is not in
On Tue, 12 Oct 1999, Herouth Maoz wrote:
> Date: Tue, 12 Oct 1999 15:22:10 +0200
> From: Herouth Maoz <[EMAIL PROTECTED]>
> To: Bruce Momjian <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Subject: Re: [ADMIN] Monitoring Database Sessions
>
> At 05:23 +0200 o
At 05:23 +0200 on 12/10/1999, Bruce Momjian wrote:
> The postmaster/postgres -d option can echo tons of information you many
>need.
> Postmaster -d will show connections, and postgres -d shows queries and
> other info. Postgres -E is good too.
If I may be so bold, I must say that the backend lo
> Good to know, but limited. to get the historical info, you'd have to continually
>spawn
> ps and either generate a lot of overhead or miss events.
>
> I think Stephen and I have roughly similar desires (ref "Logging Access" Sun, 03 Oct
>1999 23:09:06 -0400)
> It's not too hard to get the back
>> Hello,
>>
>> I was wondering if there was a way in postgres to monitor
>> database sessions.
>>
>> I'd like to be able to get a list of currently open sessions
>> with information like user id, connection time etc.
>>
>> Also I'd like to be able to see a history of sessions; again
>> user
> Hello,
>
> I was wondering if there was a way in postgres to monitor
> database sessions.
>
> I'd like to be able to get a list of currently open sessions
> with information like user id, connection time etc.
>
> Also I'd like to be able to see a history of sessions; again
> user id with ses
Hello,
I was wondering if there was a way in postgres to monitor
database sessions.
I'd like to be able to get a list of currently open sessions
with information like user id, connection time etc.
Also I'd like to be able to see a history of sessions; again
user id with session start & end tim
12 matches
Mail list logo
