| From: | Gilles Darold <gilles(at)darold(dot)net> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [BUG] pg_dump blocked |
| Date: | 2022-11-17 17:03:55 |
| Message-ID: | 8b03c83e-f2c5-3deb-6e46-99894063842f@darold.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Le 17/11/2022 à 17:59, Tom Lane a écrit :
> Gilles Darold <gilles(at)darold(dot)net> writes:
>> I have an incorrect behavior with pg_dump prior PG version 15. With
>> PostgreSQL 15, thanks to commit e3fcbbd623b9ccc16cdbda374654d91a4727d173
>> the problem is gone but for older versions it persists with locks on
>> partitioned tables.
> I didn't want to back-patch e3fcbbd62 at the time, but it's probably aged
> long enough now to be safe to back-patch. If we do anything here,
> it should be to back-patch the whole thing, else we've only partially
> fixed the issue.
I can handle this work.
--
Gilles Darold
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2022-11-17 17:04:39 | Re: SUBTRANS: Minimizing calls to SubTransSetParent() |
| Previous Message | Peter Geoghegan | 2022-11-17 17:02:48 | Re: Standardizing how pg_waldump presents recovery conflict XID cutoffs |