On Tue, Jan 16, 2018 at 07:05:19PM +0100, Adam Sjøgren wrote: > This sounds very interesting - we are running PostgreSQL 9.3.20.
Which means that we may be looking at a new bug, 9.3.20 is the latest in the 9.3 set as of today. > Did you ever find out exactly what the change that solved the problem > between 9.4.8 and 9.4.11 was? In this case, I think that you are looking for this thread: https://www.postgresql.org/message-id/20160826072658.15676.7...@wrigleys.postgresql.org And this commit: commit: a694435641faf26a9a4c210d20576ae836e86c48 author: Tom Lane <t...@sss.pgh.pa.us> date: Sat, 3 Sep 2016 13:28:53 -0400 Fix corrupt GIN_SEGMENT_ADDITEMS WAL records on big-endian hardware. Both involved 9.4.8. -- Michael
signature.asc
Description: PGP signature
