Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tender Wang <tndrwang@gmail.com>
Cc: jian he <jian.universality@gmail.com>, exclusion@gmail.com,
pgsql-bugs@lists.postgresql.org,
Amit Langote <amitlangote09@gmail.com>
Date: 2025-10-30T05:08:23Z
Lists: pgsql-bugs
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix bogus ctid requirement for dummy-root partitioned targets
- f9a468c664a4 19 (unreleased) landed
- 9f4b7bfc5eb6 18.2 landed
- 933f67fb6a79 17.8 landed
- fab386f74888 16.12 landed
- 687533b39ecf 15.16 landed
- 6d2fa44d2a61 14.21 landed
Tender Wang <tndrwang@gmail.com> writes: > I added Tom and Amit to the cc list. > Any thoughts? I'm having a hard time getting super excited about this. file_fdw does not support DELETE -- it provides no ExecForeignDelete method -- which is why you get this: regression=# DELETE FROM pt; ERROR: cannot delete from foreign table "p1" It's surely pretty accidental (and arguably not desirable) if "DELETE FROM pt WHERE false" doesn't fail the same way. Now, I agree that it's not great if you instead get an internal error like "could not find junk ctid column". But that smells to me like error checks being applied in the wrong order rather than something fundamentally wrong. I didn't look at the proposed patch yet. regards, tom lane