Re: min_safe_lsn column in pg_replication_slots view - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: min_safe_lsn column in pg_replication_slots view
Date
Msg-id 20200709005332.GA1986@alvherre.pgsql
Whole thread Raw
In response to Re: min_safe_lsn column in pg_replication_slots view  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: min_safe_lsn column in pg_replication_slots view
List 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



pgsql-hackers by date:

Previous
From: "tsunakawa.takay@fujitsu.com"
Date:
Subject: RE: Postgres is not able to handle more than 4k tables!?
Next
From: Melanie Plageman
Date:
Subject: Re: Reigning in ExecParallelHashRepartitionFirst