Horton

Re: v12 and pg_restore -f-

Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

View thread View on postgr.es
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>, Tom Lane <tgl@sss.pgh.pa.us>
Cc: Stephen Frost <sfrost@snowman.net>, "imai.yoshikazu@fujitsu.com" <imai.yoshikazu@fujitsu.com>, Euler Taveira <euler@timbira.com.br>, Andrew Gierth <andrew@tao11.riddles.org.uk>, Justin Pryzby <pryzby@telsasoft.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2019-11-05T13:47:37Z
Lists: pgsql-hackers, pgsql-general 
On 2019-11-04 15:53, Alvaro Herrera wrote:
>> No, I'm not proposing a full revert.  But there's certainly room to
>> consider reverting the part that says you*must*  write "-f -" to get
>> output to stdout.
> I don't think this will buy us anything, if we get past branches updated
> promptly.

Users with with hundreds or thousands of servers and various ancient 
maintenance scripts lying around in hard-to-track ways are not going be 
able to get everything upgraded to the latest minors *and* new script 
versions any time soon.  Until they do, they are effectively blocked 
from introducing PG12 into their environment.  This is very complicated 
and risky for them.  I think we should revert the part that requires 
using -f - at least for PG12.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Commits

  1. Change pg_restore -f- to dump to stdout instead of to ./-