| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | 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 02:38:46 |
| Message-ID: | 16DEB62F-EEBA-4BA2-AD17-8CB4290FCA5E@anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On July 26, 2018 7:33:30 PM PDT, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>On Thu, Jul 26, 2018 at 06:53:06PM -0700, Andres Freund wrote:
>> If we were to remove it, it'd obviously be a drawn out affair, given
>> that we likely couldn't drop it from the restore side immediately...
>
>The maintenance load is not high as well
Yea, I mentioned that. Worthwhile to note that it's nor pretty code.
>, so I see no real point in
>removing it, and that it would likely make people using it unhappy.
Because others have to figure out what the format is when looking at pg-dump. And might choose wrongly. That's a cost as well.
Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christophe Pettus | 2018-07-27 02:41:39 | Re: Deprecating, and scheduling removal of, pg_dump's tar format. |
| Previous Message | Peter Geoghegan | 2018-07-27 02:35:56 | Re: Deprecating, and scheduling removal of, pg_dump's tar format. |