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-21 16:32:49 |
Message-ID: | 20230221163249.orhvsut5re55fcn3@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2023-Feb-20, Alvaro Herrera wrote:
> 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.
Pushed to all three branches -- thanks, Nagata-san, for diagnosing the
issue.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"How strange it is to find the words "Perl" and "saner" in such close
proximity, with no apparent sense of irony. I doubt that Larry himself
could have managed it." (ncm, http://lwn.net/Articles/174769/)
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2023-02-21 16:33:31 | Re: refactoring relation extension and BufferAlloc(), faster COPY |
Previous Message | Nazir Bilal Yavuz | 2023-02-21 16:32:10 | Re: meson: Non-feature feature options |