Re: pgbench: \gset and \aset should store SQL NULL as the null value

From: Shinya Kato <shinya11(dot)kato(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: shihao zhong <zhong950419(at)gmail(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: pgbench: \gset and \aset should store SQL NULL as the null value
Date: 2026-09-10 11:47:04
Message-ID: CAOzEurSSY9xg_JbVEhqyY9+y1xkHFJ37D87S2rRRNpcm2cLxSw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Sep 10, 2026 at 1:16 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> The
> first test proposed is also good enough to check that we generate a
> NULL variable through setNullValue()->putVariableValue(). So kept
> only the first test, applied the result.

You're right, the first case is enough. Thanks for committing it!

--
Shinya Kato
NTT OSS Center

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nisha Moond 2026-09-10 11:51:01 Re: Crashes on a partition whose concurrent detach never finished
Previous Message Nazir Bilal Yavuz 2026-09-10 11:45:03 Re: CI slowdown due to PG_TEST_INITDB_EXTRA_OPTS