From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Jan Wieck <JanWieck(at)Yahoo(dot)com>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [GENERAL] Stats Collector |
Date: | 2002-07-30 20:04:45 |
Message-ID: | 200207302004.g6UK4jg18177@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> >> It all works now and I have just submitted it to -patches as a new contrib,
> >> but it probably should make its way into the backend one day.
>
> > OK, the big question is how do we want to make stats reset visible to
> > users? The current patch uses a function call. Is that how we want to
> > do it?
>
> Should we make it visible at all? I'm concerned about security.
Yea, as long as it is in contrib, only the super-user can install it,
but once installed, anyone can run it, I think.
A function seems like the wrong way to go on this. SET has super-user
protections we could use to control this but I am not sure what SET
syntax to use.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Clift | 2002-07-30 20:21:23 | Have been accepted as a writer for "The Register" |
Previous Message | Tom Lane | 2002-07-30 19:55:38 | Re: [GENERAL] Stats Collector |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-07-30 20:17:51 | Re: WAL file location |
Previous Message | Tom Lane | 2002-07-30 19:55:38 | Re: [GENERAL] Stats Collector |