From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Anthonin Bonnefoy <anthonin(dot)bonnefoy(at)datadoghq(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: Consider pipeline implicit transaction as a transaction block |
Date: | 2024-11-27 15:35:09 |
Message-ID: | CAGECzQQS1Oun40BssQDmuHc86teXqr+LOndy5NSVdFce9evZvQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 27 Nov 2024 at 01:42, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> I've edited the whole, added this extra test based on \syncpipeline in
> 17~, kept the remaining tests in 14~ where pgbench is able to handle
> them, and backpatched that down to 13. Let's see now what we can do
> with the psql bits.
FYI: it turns out this change broke one of the tests on our pg_duckdb
repo[1] because the error message that PreventInTranasctionBlock
throws is now different:
E AssertionError: Regex pattern did not match.
E Regex: 'DuckDB queries cannot be executed within a pipeline'
E Input: 'DuckDB queries cannot run inside a transaction block'
I personally don't think that's particularly bad, or revert-worthy,
but the previous error was a bit clearer IMO. I don't see how we can
still show it with the new code though.
[1]: https://github.com/duckdb/pg_duckdb/actions/runs/12052926038/job/33607381526?pr=453#step:15:51
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Pryzby | 2024-11-27 15:35:16 | Re: Don't overwrite scan key in systable_beginscan() |
Previous Message | Peter Eisentraut | 2024-11-27 15:33:25 | Re: Don't overwrite scan key in systable_beginscan() |