Re: Continue work on changes to recovery.conf API

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Sergei Kornilov <sk(at)zsrv(dot)org>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Continue work on changes to recovery.conf API
Date: 2018-11-25 19:16:16
Message-ID: 17932.1543173376@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> Committed with that addition.

Some of the buildfarm doesn't like this. I realized that the common
denominator was EXEC_BACKEND: if you build with -DEXEC_BACKEND the
failure is completely reproducible. Presumably something is thinking
that it will inherit some variable from the postmaster via fork.
I don't know if that's a new bug or was just exposed by a new test.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Laurenz Albe 2018-11-25 19:17:30 Re: Updated backup APIs for non-exclusive backups
Previous Message Stephen Frost 2018-11-25 18:50:17 Re: Updated backup APIs for non-exclusive backups