| From: | Kamigishi Rei <iijima(dot)yun(at)koumakan(dot)jp> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de>, Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, David Rowley <dgrowley(at)gmail(dot)com>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17245: Index corruption involving deduplicated entries |
| Date: | 2021-10-29 08:17:49 |
| Message-ID: | 58e5e313-ba8d-ba52-724f-c8563b547af1@koumakan.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 29.10.2021 1:48, Andres Freund wrote:
> That wouldn't protect against e.g. a logic bug in ZFS. Given its copy-on-write
> nature corruption could very well manifest as seeing an older version of the
> data when re-reading data from disk. Which could very well lead to the type of
> corruption we're seeing here.
> Didn't 14 change the logic when index vacuums are done? That could cause
> previously existing issues to manifest with a higher likelihood.
Note that I ran 13.2 (that came with open_datasync()) and 13.3 (which
switched back to fdatasync()) on openzfs for almost a year since
upgrading to 13.0-RELEASE, with no discernible issues. The 13.3 data
directory has been kept intact since the upgrade to 14.
--
K. R.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Herman verschooten | 2021-10-29 08:47:34 | Re: ERROR: posting list tuple with 20 items cannot be split at offset 168 |
| Previous Message | Kamigishi Rei | 2021-10-29 08:12:07 | Re: BUG #17245: Index corruption involving deduplicated entries |