From: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Jan Wieck <JanWieck(at)Yahoo(dot)com>, PostgreSQL HACKERS <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Configuration of statistical views |
Date: | 2001-06-29 16:10:09 |
Message-ID: | 200106291610.f5TGA9P03841@jupiter.us.greatbridge.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian wrote:
> > If somebody wants to see an applications querystring (at
> > least the first 512 bytes) just in case something goes wrong
> > and the client hangs, he'd have to run querystring reporting
> > all the time either way.
>
> Agreed. That should be on all the time.
>
> > So I can see value in a per database default in pg_database
> > plus the ability to switch it on/off via statement to analyze
> > single commands.
>
> Sounds fine. You may be able to just to a GUC/SET option and not do a
> per-database field. GUC doesn't do per-database and having a database
> flag and GUC would be confusing. Let's roll with just GUC/SET and see
> how it goes.
No per backend on/off statement - is that what you mean?
That'd be easiest to get started.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-06-29 16:21:05 | Re: Configuration of statistical views |
Previous Message | Alex Perel | 2001-06-29 16:09:05 | Re: Postgres to Dia UML |