Re: v12 and pg_restore -f-

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, "imai(dot)yoshikazu(at)fujitsu(dot)com" <imai(dot)yoshikazu(at)fujitsu(dot)com>, Euler Taveira <euler(at)timbira(dot)com(dot)br>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: v12 and pg_restore -f-
Date: 2019-11-05 15:07:39
Message-ID: 20191105150739.GA6833@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On 2019-Nov-05, Tom Lane wrote:

> Sure, because there wasn't any practical way to provide a transition
> period. I think that case is entirely not comparable to this one,
> either as to whether a transition period is possible, or as to whether
> the benefits of the change merit forced breakage.

We're not forcing anyone into upgrading. Older versions continue to
work, and many people still use those. People who already upgraded
and needed a cross-version scriptable mechanism can already use
"-f/dev/stdout" as Justin documented in this thread's OP. People
upgrading after next week release set can use "-f-". People not
upgrading soon can keep their scripts for a while yet.

I think this teapot doesn't need the tempest, and nobody's drowning in
it anyway.

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Imre Samu 2019-11-05 15:09:42 Re: How to import Apache parquet files?
Previous Message Peter Eisentraut 2019-11-05 15:02:51 Re: logical replication - negative bitmapset member not allowed

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2019-11-05 15:16:41 Re: cost based vacuum (parallel)
Previous Message Tom Lane 2019-11-05 15:04:14 Re: Keep compiler silence (clang 10, implicit conversion from 'long' to 'double' )