, especially
in
setups that would like to minimize cross-language scripting/dependencies.
However, I also understand that this isn't exactly how Postgres might be
commonly used on these mailing lists.
—David
On Oct 13, 2025 at 1:27:17 PM, Ron Johnson wrote:
> On Mon, Oct 13, 2025 at
> "Testing" db interaction in a faked, circumscribed
> only-my-stuff-is-there world is folly. Certainly each db developer
> needs their own instance of the database (on their own box or a
> server). And it needs to be kept current with both DDL and domain meta
> data changes (see things like flyway
Yeah. Something like this, which we don't have:
> postgres -c "auto_close=on"
An API surface like that would be nice, but doesn’t need to be `postgres`.
I’m not picky.
Best,
David
On Oct 11, 2025 at 4:11:18 PM, Adrian Klaver
wrote:
> On 10/8/25 12:39, David Barsky w
Hiya folks,
I'm a bit of a newcomer when it comes to PostgreSQL, so I apologize if this
is
the wrong mailing list. Anyways, my two questions:
1. Is there any interest in adding a command line option to the `postgres`
CLI
that shuts down the PostgreSQL instance once (and optionally cleans up
th
