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

Re: show all;

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 (view raw or flat)
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


In response to

Responses

pgsql-patches by date

Next:From: Tom LaneDate: 2001-06-02 15:23:39
Subject: Re: show all;
Previous:From: Tom LaneDate: 2001-06-02 15:04:05
Subject: Re: Fw: Isn't pg_statistic a security hole - Solution Proposal

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