| From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, iijima(dot)yun(at)koumakan(dot)jp |
| Subject: | Re: BUG #17245: Index corruption involving deduplicated entries |
| Date: | 2021-10-25 00:56:36 |
| Message-ID: | 87pmru6i9u.fsf@news-spur.riddles.org.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
>>>>> "Peter" == Peter Geoghegan <pg(at)bowt(dot)ie> writes:
Peter> PostgreSQL 14 is the first version where the default
Peter> wal_sync_method is fdatasync() on FreeBSD -- though only with
Peter> FreeBSD 13. See commit f900a79e. Perhaps that has something to
Peter> do with the problem seen here.
Nope. The database in question was restored from a pg_dumpall backup
three weeks ago and I'm told there have been no crashes or even unclean
restarts since then.
Peter> I suspect that there was TID recycling by VACUUM involved here.
That also doesn't seem likely from the heap page images I saw, which
suggested a fairly low update rate, HOT updates, and page cleanup rather
than much vacuum activity (in particular there were several LP_REDIRECT
pointers and few free pointers).
--
Andrew (irc:RhodiumToad)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2021-10-25 01:04:41 | Re: BUG #17245: Index corruption involving deduplicated entries |
| Previous Message | Tom Lane | 2021-10-24 23:53:19 | Re: conchuela timeouts since 2021-10-09 system upgrade |