Re: Bug in pgbench prepared statements

so catching the error from PQsendQueryPrepared() is exactly what's causing the bug: ERROR: prepared statement "P_0" does not exist. Best, Lev postgresml.org On Thu, Nov 30, 2023 at 11:19 PM Michael Paquier wrote: > On Thu, Nov 30, 2023 at 07:15:54PM -0800, Lev Kokotov wrote: > >&g

Re: Bug in pgbench prepared statements

mmit it. First time contributing, not familiar with the process here, but happy to learn. Best, Lev postgresml.org On Thu, Nov 30, 2023 at 2:10 PM Tristan Partin wrote: > On Wed Nov 29, 2023 at 7:38 PM CST, Lev Kokotov wrote: > > Patch attached, if there is any interest in fixing t

Bug in pgbench prepared statements

Hi, I noticed something that looks like a bug in pgbench when using the prepared protocol. pgbench assumes that all prepared statements are prepared correctly, even if they contain errors (e.g. syntax, column/table doesn't exist, etc.). My test script is just: SELECT one; The output looks

Add "host" to startup packet

Hello, Patch attached below. TLDR, I'd like to add "host" to the startup packet. I'm trying to run multiple Postgres servers in a multi-tenant environment behind a pooler . Currently, the only way to differentiate Postgres databases is with the user/dbname

Re: Support for Rust

will have to be rewritten, so not a short and easy migration. Best, Lev [0] https://github.com/tcdi/pgx [1] https://docs.rust-embedded.org/book/intro/index.html On Sat, Sep 10, 2022 at 10:15 AM Nathan Bossart wrote: > On Fri, Sep 09, 2022 at 07:38:14PM -0700, Lev Kokotov wrote: > > Are

Support for Rust

Hello, Are there any plans or thoughts about adding support for other languages than C into Postgres, namely Rust? I would love to hack on some features but I worry somewhat that the C compiler won't give me enough hints that I'm doing something wrong, and the Rust compiler has been excellent at