| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
| Cc: | Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>, Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pgbench: using prepared BEGIN statement in a pipeline could cause an error |
| Date: | 2023-05-22 11:49:47 |
| Message-ID: | 20230522114947.4lvw3hxur3pjkx27@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2023-May-20, Alexander Lakhin wrote:
> Starting from 038f586d5, the following script:
> echo "
> \startpipeline
> \endpipeline
> " >test.sql
> pgbench -n -M prepared -f test.sql
>
> leads to the pgbench's segfault:
Hah, yeah, that's because an empty pipeline never calls the code to
allocate the flag array. Here's the trivial fix.
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"El hombre nunca sabe de lo que es capaz hasta que lo intenta" (C. Dickens)
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Fix-pgbench-in-prepared-mode-with-empty-pipeline.patch | text/x-diff | 2.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2023-05-22 11:52:24 | Re: Adding SHOW CREATE TABLE |
| Previous Message | Hayato Kuroda (Fujitsu) | 2023-05-22 11:49:12 | RE: Time delayed LR (WAS Re: logical replication restrictions) |