| From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, 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 04:03:46 |
| Message-ID: | CANzqJaCydWJm8utvhLMWy62MGRYP0qdK134WB8NzXTJf=KUEPg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Jan 27, 2026 at 10:52 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "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).
Hmm. Must have been START TRANSACTION which I remember causing issues in DO
blocks.
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-01-28 04:06:41 | Re: Attempting to delete excess rows from table with BATCH DELETE |
| Previous Message | Ron Johnson | 2026-01-28 03:57:56 | Re: Attempting to delete excess rows from table with BATCH DELETE |