Check invalid pages at the end of recovery to alarm lost data

2023-07-10 Thread ()
hello, all. Recently, I find one very strange situation to lose data of primary node which the details can be find at the first patch: 0001-Add-test-case-data-lost-after-restart.patch. The first patch shows us that data could be lost after truncating physical file by someone else before startin

why doesn't call XLogCheckInvalidPages during primary crash recovery?

2023-07-03 Thread ()
Hi hackers, Startup process will record not existed pages into hash table invalid_page_tab during replaying WAL. And it would call XLogCheckInvalidPages after reaching consistent recovery state. Finally, it will PANIC or WARNING based on parameter ignore_invalid_pages if where's any invalid page

回复:Re: PANIC: wrong buffer passed to visibilitymap_clear

2022-07-26 Thread ()
On Fri, Jul 22, 2022 at 14:49 Peter Geoghegan wrote: > The line numbers from your stack trace don't match up with> REL_14_STABLE. Is > this actually a fork of Postgres 14? (Oh, looks like > it's an old beta release.) Yeah, I was testing on 14beta2 branch once. So I considered your advices and tes

回复:Re: PANIC: wrong buffer passed to visibilitymap_clear

2022-07-22 Thread ()
---- 发件人:Tomas Vondra 日 期:2022年07月22日 18:06:21 收件人:王伟(学弈); pgsql-hackers 主 题:Re: PANIC: wrong buffer passed to visibilitymap_clear On 7/22/22 10:22, 王伟(学弈) wrote: > Hi, > I recently find this problem while testing PG14 with sysbench. > Then I look through

PANIC: wrong buffer passed to visibilitymap_clear

2022-07-22 Thread ()
Hi, I recently find this problem while testing PG14 with sysbench. Then I look through the emails from pgsql-hackers and find a previous similary bug which is https://www.postgresql.org/message-id/flat/2247102.1618008027%40sss.pgh.pa.us. But the bugfix commit(34f581c39e97e2ea237255cf75cccebccc02