| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | pgbf(at)twiska(dot)com, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: XLogReadRecord() error in XlogReadTwoPhaseData() |
| Date: | 2022-01-20 19:34:22 |
| Message-ID: | CA+hUKGL0LjbtKjN_zKBas0rd40iPbVs2a-DijBd74cjb4_M9Fw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jan 17, 2022 at 10:02 AM Noah Misch <noah(at)leadboat(dot)com> wrote:
> - Report a Debian bug for the sparc64+ext4 zeros problem.
I suspect that 027_stream_regress.pl hits this kernel bug with high
probability[1]. I wonder if the owner of kittiwake and tadarida would
consider setting up an xfs file system? Or alternatively, since ext4
didn't support concurrent writes until recently, I wonder if there is
an option somewhere to turn the new concurrency stuff off, or failing
that, if we could temporarily downgrade the kernel to an older version
that does inode-level read/write locking.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2022-01-20 19:38:15 | Re: preserving db/ts/relfilenode OIDs across pg_upgrade (was Re: storing an explicit nonce) |
| Previous Message | Ilaria Battiston | 2022-01-20 19:33:28 | GSoC 2022 |