| From: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Subject: | Re: Run pg_amcheck in 002_pg_upgrade.pl and 027_stream_regress.pl? |
| Date: | 2022-04-04 16:30:11 |
| Message-ID: | A549DD76-8DEC-41AE-9193-76683B2471C0@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Apr 4, 2022, at 9:27 AM, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
>
> I'd really like it if amcheck had HOT chain verification. That's the
> other area where catching bugs passively with assertions and whatnot
> is clearly not good enough.
I agree, and was hoping to get around to this in the postgres 15 development cycle. Alas, that did not happen. Worse, I have several other projects that will keep me busy for the next few months, at least.
—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Rouhaud | 2022-04-04 16:31:38 | Re: Showing I/O timings spent reading/writing temp buffers in EXPLAIN |
| Previous Message | Peter Geoghegan | 2022-04-04 16:27:06 | Re: Run pg_amcheck in 002_pg_upgrade.pl and 027_stream_regress.pl? |