From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: crash testing suggestions for 12 beta 1 |
Date: | 2019-06-05 21:11:38 |
Message-ID: | 20190605211138.GA15768@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2019-May-23, Jeff Janes wrote:
> Now that beta is out, I wanted to do some crash-recovery testing where I
> inject PANIC-inducing faults and see if it recovers correctly. A long-lived
> Perl process keeps track of what it should find after the crash, and
> verifies that it finds it. You will probably be familiar with the general
> theme from examples like the threads below. Would anyone like to nominate
> some areas to focus on?
Thanks for the offer! Your work has showed its value in previous cycles.
REINDEX CONCURRENTLY would be one good area to focus on, I think, as
well as ALTER TABLE ATTACH PARTITION. Maybe also INCLUDE columns in
GiST, and the stuff in commits 9155580fd, fe280694d and 7df159a62.
Thanks,
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2019-06-05 21:32:49 | Re: crash testing suggestions for 12 beta 1 |
Previous Message | Alvaro Herrera | 2019-06-05 20:54:24 | Re: Cleaning up and speeding up string functions |