| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Amul Sul <sulamul(at)gmail(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: new heapcheck contrib module |
| Date: | 2020-09-22 17:58:21 |
| Message-ID: | CAH2-WzmuQSXmweXeS5V3_hzR0KpDqF=JMeLYZ6-89KB3r3Uj4w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Sep 22, 2020 at 10:55 AM Mark Dilger
<mark(dot)dilger(at)enterprisedb(dot)com> wrote:
> I am inclined to just restrict verify_heapam() to superusers and be done. What do you think?
The existing amcheck functions were designed to have execute privilege
granted to non-superusers, though we never actually advertised that
fact. Maybe now would be a good time to start doing so.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2020-09-22 18:29:33 | Re: SEARCH and CYCLE clauses |
| Previous Message | Mark Dilger | 2020-09-22 17:55:35 | Re: new heapcheck contrib module |