public inbox for [email protected]
help / color / mirror / Atom feedFrom: Kirk Wolak <[email protected]>
To: PostgreSQL Hackers <[email protected]>
Subject: pgbench: can we add a way to specify the schema to write to?
Date: Mon, 15 May 2023 21:35:54 -0400
Message-ID: <CACLU5mSuOCkCG2ApPdE5F5zxwF_reMj0rNMkvecAvNZuX2VPnQ@mail.gmail.com> (raw)
Currently, I believe that we are frowning on writing things directly to
Public by default.
Also, we had already taken that step in our systems. Furthermore we force
Public to be the first Schema, so this restriction enforces that everything
created must be assigned to the appropriate schema.
That could make us a bit more sensitive to how pgbench operates. But this
becomes an opportunity to sharpen a tool.
But logging in to our regular users it has no ability to create it's tables
and do it's work. At the same time, we want exactly this login, because we
want to benchmark things in our application.
Our lives would be simplified if there was a simple way to specify a schema
for pgbench to use. It would always reference that schema, and it would
not be in the path. Making it operate "just like our apps" while benching
marking our items.
While we are here, SHOULD we consider having pgbench have a default schema
name it creates and then cleans up? And then if someone wants to override
that, they can?
Kirk...
view thread (2+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: pgbench: can we add a way to specify the schema to write to?
In-Reply-To: <CACLU5mSuOCkCG2ApPdE5F5zxwF_reMj0rNMkvecAvNZuX2VPnQ@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox