| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Ahsan Hadi <ahsan(dot)hadi(at)gmail(dot)com> |
| Cc: | Asif Rehman <asifr(dot)rehman(at)gmail(dot)com>, Jeevan Chalke <jeevan(dot)chalke(at)enterprisedb(dot)com>, Kashif Zeeshan <kashif(dot)zeeshan(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Rajkumar Raghuwanshi <rajkumar(dot)raghuwanshi(at)enterprisedb(dot)com> |
| Subject: | Re: WIP/PoC for parallel backup |
| Date: | 2020-04-15 13:31:22 |
| Message-ID: | CA+TgmoZsfpsqqVqYu2V9LAKoBzg8yAGiSuoL5icNcZciCL1arQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Apr 15, 2020 at 4:49 AM Ahsan Hadi <ahsan(dot)hadi(at)gmail(dot)com> wrote:
> Fair enough. Some of this is also due to backup related features i.e backup manifest, progress reporting that got committed to master towards the tail end of PG-13. Rushing to get parallel backup feature compatible with these features also caused some of the oversights.
Sure, but there's also no point in rushing out a feature that's in a
state where it's got no chance of being acceptable, and quite a number
of these problems are not new, either.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James Coleman | 2020-04-15 13:31:58 | Re: [DOC] Document concurrent index builds waiting on each other |
| Previous Message | Robert Haas | 2020-04-15 13:24:38 | Re: documenting the backup manifest file format |