| From: | Marko Kreen <marko(at)l-t(dot)ee> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: show all; |
| Date: | 2001-06-02 15:14:04 |
| Message-ID: | 20010602171404.A21968@l-t.ee |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
On Sat, Jun 02, 2001 at 10:31:52AM -0400, Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > The issue is that it fills the logs if used a lot:
> Some ideas to think about:
>
> 1. Invent SET variables to control the minimum elog severity level
> that gets into the logs or sent to the client, rather than hard-wiring
> these levels at DEBUG and NOTICE respectively.
I assume 'RESET ALL' should clear the var, so it should be set
in beginning each pooled connection use?
--
marko
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-06-02 15:23:39 | Re: show all; |
| Previous Message | Tom Lane | 2001-06-02 15:04:05 | Re: Fw: Isn't pg_statistic a security hole - Solution Proposal |