| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Gus Spier <gus(dot)spier(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Attempting to delete excess rows from table with BATCH DELETE |
| Date: | 2026-01-28 03:52:00 |
| Message-ID: | 729685.1769572320@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Tuesday, January 27, 2026, Gus Spier <gus(dot)spier(at)gmail(dot)com> wrote:
>> I write a procedure to accomplish all this work but it persists in
>> returning a error to the effect that a COMMIT is not valid in a block
>> tht tries to DELETE data.
> Haven’t tested to be sure but this doesn’t seem like a community edition
> limitation.
Yeah, you can definitely do that in standard Postgres (at least since
we invented procedures). Sounds like Aurora is behind the times.
I know that their storage engine is fundamentally different from ours;
perhaps it has problems with this idea.
> You’d have to move the logic to a proper client application that executes
> top-level commands.
Yup.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2026-01-28 03:57:56 | Re: Attempting to delete excess rows from table with BATCH DELETE |
| Previous Message | David G. Johnston | 2026-01-28 03:39:03 | Re: Attempting to delete excess rows from table with BATCH DELETE |