Re: TOAST corruption in standby database

2019-10-28 Thread postgresql_2...@163.com
SELECT ctid, chunk_id, chunk_seq, md5(chunk_data) FROM pg_toast.pg_toast_16103925 WHERE chunk_id = 64265646; ctid | chunk_id | chunk_seq | md5 --+--+---+- (0 rows) SELECT count(1) FROM pg_toast.pg_toast_16103925 WHERE chunk_id = 64265646; count --- 2 (1 row) >Fr

Re: TOAST corruption in standby database

2019-10-26 Thread Amit Kapila
On Fri, Oct 25, 2019 at 1:50 AM Alex Adriaanse wrote: > > Standby (corrupted): > > # dd if=data/base/18034/16103928.13 bs=8192 skip=89185 count=1 status=none | > hexdump -C | head -8 > a3 0e 00 00 48 46 88 0e 00 00 05 00 30 00 58 0f |HF..0.X.| > 0010 00 20 04 20 00 00 00

TOAST corruption in standby database

2019-10-24 Thread Alex Adriaanse
We have primary and hot standby databases running Postgres 11.3 inside Docker, with their data directories bind-mounted to a reflink-enabled XFS filesystem. The VM is running Debian's 4.19.16-1~bpo9+1 kernel inside an AWS EC2 instance. I've seen TOAST corruption in one of the standby databases a