| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Peter Geoghegan <pg(at)bowt(dot)ie> |
| Subject: | Re: new heapcheck contrib module |
| Date: | 2020-04-29 17:28:53 |
| Message-ID: | CA+TgmobyO1C8Gqjf3orhS1q60HXqnw6EL=Ss-Dy9uAOqog62Jg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Apr 29, 2020 at 12:30 PM Mark Dilger
<mark(dot)dilger(at)enterprisedb(dot)com> wrote:
> Do you think it would make sense to have the amcheck contrib module have, in addition to the SQL queriable functions, a bgworker based mode that periodically checks your database? The work along those lines is not included in v4, but if it were part of v5, would you have specific design preferences?
-1 on that idea from me. That sounds like it's basically building
"cron" into PostgreSQL, but in a way that can only be used by amcheck.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-04-29 18:02:34 | Re: SEQUENCE values (duplicated) in some corner cases when crash happens |
| Previous Message | Mark Dilger | 2020-04-29 16:30:28 | Re: new heapcheck contrib module |