From: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(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 15:51:11 |
Message-ID: | 200106291551.f5TFpB303705@jupiter.us.greatbridge.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Jan Wieck <JanWieck(at)Yahoo(dot)com> writes:
> > 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.
>
> Do you even need a per-database default? Why not an installation-wide
> default in postgresql.conf plus on/off commands? The great advantage
> of doing it that way is that it's simply a GUC variable or three, and
> you don't need to expend any work on developing infrastructure. So
> I'd recommend doing it that way to get started, even if you later decide
> that something more complex is warranted.
Personally, I can live with no options at all, because I
think that amount of performance loss is worth it beeing able
to look at a query in case. You know, if it's a config option
it tends to allways being off when the errors happen.
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 15:53:15 | Re: Configuration of statistical views |
Previous Message | Matthew T. O'Connor | 2001-06-29 15:34:17 | Help with SI buffer overflow error |