| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Kamigishi Rei <iijima(dot)yun(at)koumakan(dot)jp> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, 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 19:08:19 |
| Message-ID: | CAH2-WzmKsFWBG_WRSUQ+GWrV=Bi7_XjFjs4S2sESrQ-wMRApSA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Oct 29, 2021 at 1:17 AM Kamigishi Rei <iijima(dot)yun(at)koumakan(dot)jp> wrote:
> 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.
I now think that this is very likely to be a bug in Postgres 14. Note
that another user with very similar corruption (same symptoms, similar
workload) happened to be using ext4 on Linux.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kamigishi Rei | 2021-10-29 19:19:06 | Re: BUG #17245: Index corruption involving deduplicated entries |
| Previous Message | Peter Geoghegan | 2021-10-29 19:05:45 | Re: BUG #17245: Index corruption involving deduplicated entries |