Re: BUG #15116: pg_recvlogical always fails

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, kotlarski(dot)krzysztof(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15116: pg_recvlogical always fails
Date: 2018-03-17 23:02:41
Message-ID: 20180317230241.GA19730@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sat, Mar 17, 2018 at 06:33:48PM +0100, Magnus Hagander wrote:
> In this scenario, since we don't actively *enforce* this version
> difference, I think we should apply the fix from #1 in this scenario as
> well. Otherwise you might use an old pg_recvlogical to connect to a newer
> server, and open up a vulnerability somehow. I assume pg_recvlogical of
> that age doesn't actually try to do something with it, but it still feels
> safer for the future.

Yeah, there is no actual reason to not apply #1 everywhere as well. The
back-patch is a no-brainer.
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2018-03-17 23:28:12 Re: BUG #15115: temporary AND unlogged tables for parallel db import
Previous Message Petar Bogdanovic 2018-03-17 20:55:44 Re: BUG #15120: use of getcwd(3)/chdir(2) during path resolution (exec.c)