> On Oct 11, 2021, at 11:26 AM, Peter Geoghegan <p...@bowt.ie> wrote: > > We should have a warning box about this in the pg_amcheck docs. Users > should think carefully about ever using --parent-check, since it alone > totally changes the locking requirements (actually --rootdescend will > do that too, but only because that option also implies > --parent-check). The recently submitted patch already contains a short paragraph for each of these, but not a warning box. Should I reformat those as warning boxes? I don't know the current thinking on the appropriateness of that documentation style. — Mark Dilger EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
- Re: BUG #17212: pg_amcheck fails on ... Peter Geoghegan
- Re: BUG #17212: pg_amcheck fails on ... Mark Dilger
- Re: BUG #17212: pg_amcheck fails on ... Peter Geoghegan
- Re: BUG #17212: pg_amcheck fails on ... Mark Dilger
- Re: BUG #17212: pg_amcheck fails on ... Peter Geoghegan
- Re: BUG #17212: pg_amcheck fails on ... Mark Dilger
- Re: BUG #17212: pg_amcheck fails on ... Peter Geoghegan
- Re: BUG #17212: pg_amcheck fails on ... Mark Dilger
- Re: BUG #17212: pg_amcheck fails on ... Peter Geoghegan
- Re: BUG #17212: pg_amcheck fails on ... Peter Geoghegan
- Re: BUG #17212: pg_amcheck fails on ... Mark Dilger
- Re: BUG #17212: pg_amcheck fails on ... Peter Geoghegan
- Re: BUG #17212: pg_amcheck fails on ... Mark Dilger
- Re: BUG #17212: pg_amcheck fails on ... Peter Geoghegan
- Re: BUG #17212: pg_amcheck fails on checking temporary rel... Peter Geoghegan