Re: min_safe_lsn column in pg_replication_slots view
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgbf@twiska.com, Kyotaro Horiguchi <horikyota.ntt@gmail.com>, masao.fujii@oss.nttdata.com, pgsql-hackers@lists.postgresql.org
Date: 2020-07-09T00:53:32Z
Lists: pgsql-hackers
On 2020-Jul-08, Tom Lane wrote: > Alvaro Herrera <alvherre@2ndquadrant.com> writes: > > Ouch. So 12 builds with -O0 but 13 does not? > > Unless Tom's changed the animal's config since that thread, yes. I verified the configs in branches 12 and 13 in one of the failing animals, and yes that's still the case. > > Did we do something to > > sequence.c to work around this problem? I cannot find anything. > > We did not. If it's a compiler bug, and one as phase-of-the-moon- > dependent as this seems to be, I'd have zero confidence that any > specific source code change would fix it (barring someone confidently > explaining exactly what the compiler bug is, anyway). The best we > can do for now is hope that backing off the -O level avoids the bug. An easy workaround might be to add -O0 for that platform in that directory's Makefile. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Fix uninitialized value in segno calculation
- b5b4c0fef9fb 14.0 landed
- 794e8e32bb5a 13.0 landed
-
Morph pg_replication_slots.min_safe_lsn to safe_wal_size
- c54b5891f415 13.0 landed
- a8aaa0c786b3 14.0 landed