| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>, 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-02-20 20:17:47 |
| Message-ID: | 20230220201747.4fblwswxq3xbgz2c@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Found one last problem: if you do "-f foobar.sql -M prepared" in that
order, then the prepare fails because the statement names would not be
assigned when the file is parsed. This coding only supported doing
"-M prepared -f foobar.sql", which funnily enough is the only one that
PostgreSQL/Cluster.pm->pgbench() supports. So I moved the prepared
statement name generation to the postprocess step.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"La rebeldía es la virtud original del hombre" (Arthur Schopenhauer)
| Attachment | Content-Type | Size |
|---|---|---|
| v9-0001-pgbench-Prepare-commands-in-pipelines-in-advance.patch | text/x-diff | 9.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-02-20 20:48:04 | Re: Killing off removed rels properly |
| Previous Message | Dean Rasheed | 2023-02-20 19:49:56 | Allow MERGE to be executed from PL/Tcl |