From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Removing remaining parallel-build hazards in ecpg
Date: Fri, 30 Nov 2018 10:50:04 +0900
Message-ID: <20181130015004.GD2267@paquier.xyz> (raw)
In-Reply-To: <31364.1543511708@sss.pgh.pa.us>
References: <31364.1543511708@sss.pgh.pa.us>
On Thu, Nov 29, 2018 at 12:15:08PM -0500, Tom Lane wrote:
> I'm also wondering whether to back-patch such a change. Since we've
> not heard field complaints that match up to this problem, it may be
> that it's unlikely enough that fixing it in HEAD is good enough.
HEAD sounds good enough for to me. Thanks for looking at those issues!
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: michael@paquier.xyz, tgl@sss.pgh.pa.us, pgsql-hackers@lists.postgresql.org
Subject: Re: Removing remaining parallel-build hazards in ecpg
In-Reply-To: <20181130015004.GD2267@paquier.xyz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox