| From: | Andreas Karlsson <andreas(at)proxel(dot)se> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: dblink query interruptibility |
| Date: | 2025-03-12 10:03:41 |
| Message-ID: | ed82a883-d751-4e61-977b-a7a1150dbf32@proxel.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/12/25 12:48 AM, Noah Misch wrote:
> The CREATE DATABASE hang is indeed new in v15. The general dblink missed
> interrupt processing (e.g. pg_cancel_backend response delay) is an old bug.
Aha, that was what you were referring to! My apologies, was reading your
mail a bit too quickly. :)
> Commit d3c5f37 used the new functions for postgres_fdw, not just dblink. That
> caused message changes detailed in
> postgr.es/m/CAHGQGwGpDTXeg8K1oTmDv9nankaKTrCD-XW-tnkzo6%3DE9p5%3Duw%40mail.gmail.com
> so I'm inclined to omit postgres_fdw changes in back branches. postgres_fdw
> was already interruptible, so the point of making postgres_fdw adopt the
> functions was to reduce code duplication.
Makes sense.
> Overall, in the absence of objections, I will queue a task to back-patch the
> non-postgres_fdw portion of commit d3c5f37 to v13-v16.
Thanks!
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rushabh Lathia | 2025-03-12 10:04:12 | Re: Support NOT VALID / VALIDATE constraint options for named NOT NULL constraints |
| Previous Message | Amul Sul | 2025-03-12 10:02:07 | Re: NOT ENFORCED constraint feature |