| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org,Christophe Pettus <xof(at)thebuild(dot)com>,Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Peter Geoghegan <pg(at)bowt(dot)ie>,Michael Paquier <michael(at)paquier(dot)xyz>,PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>,Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
| Subject: | Re: Deprecating, and scheduling removal of, pg_dump's tar format. |
| Date: | 2018-07-27 03:22:44 |
| Message-ID: | D848B8CD-F955-4B60-AF55-DE0F1049FA4D@anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On July 26, 2018 8:14:57 PM PDT, Christophe Pettus <xof(at)thebuild(dot)com> wrote:
>
>> On Jul 26, 2018, at 20:09, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
>>
>> Do you, perhaps, have any insight into why those users are currently
>> using the .tar format?
>
>Inertia, in most cases; some of those procedures have been around since
>8.1 days. Custom format (or a tar'd parallel dump) would be an
>undoubtedly superior choice. A long depreciation window would cover a
>lot of those situations.
Yea, that obviously would be called for (see also the subject of my email). I'd assume we'd do something like deprecating the dump side in 12, removing it in 13. The restore side would then be removed in 12+5. Or similar.
Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro HORIGUCHI | 2018-07-27 03:37:02 | Re: BUG #15182: Canceling authentication due to timeout aka Denial of Service Attack |
| Previous Message | Fabien COELHO | 2018-07-27 03:16:06 | pgbench - very minor bug fix on hash() missing argument |