Marco Mariani <marco (AT) sferacarta (DOT) com> writes:

I'm not interested in "performance", but rather reduction in external
dependencies for unit tests (i.e. unit tests should not rely on a
running database server).

Now that we've established that I want what I actually asked for, can
someone give suggestions on how to achieve it?

--
\ "If you can't annoy somebody there is little point in writing." |
`\ -- Kingsley Amis |
_o__) |
Ben Finney

Ben Finney wrote:

I'm not sure I understand.
You cannot connect to postgres and use all of the postgres features,
like you asked, withouth connecting to a running database server.

Is this what you're asking?

Because.. with sqlite in RAM you _ARE_ using the whole stack of the
database, only there is no separate server process.

Ben Finney wrote:

I'm not sure I understand.
You cannot connect to postgres and use all of the postgres features,
like you asked, withouth connecting to a running database server.

Is this what you're asking?

Because.. with sqlite in RAM you _ARE_ using the whole stack of the
database, only there is no separate server process.

Ben Finney wrote:

I'm not sure I understand.
You cannot connect to postgres and use all of the postgres features,
like you asked, withouth connecting to a running database server.

Is this what you're asking?

Because.. with sqlite in RAM you _ARE_ using the whole stack of the
database, only there is no separate server process.

Ben Finney wrote:

I'm not sure I understand.
You cannot connect to postgres and use all of the postgres features,
like you asked, withouth connecting to a running database server.

Is this what you're asking?

Because.. with sqlite in RAM you _ARE_ using the whole stack of the
database, only there is no separate server process.

Ben Finney wrote:

I'm not sure I understand.
You cannot connect to postgres and use all of the postgres features,
like you asked, withouth connecting to a running database server.

Is this what you're asking?

Because.. with sqlite in RAM you _ARE_ using the whole stack of the
database, only there is no separate server process.

Ben Finney wrote:

I'm not sure I understand.
You cannot connect to postgres and use all of the postgres features,
like you asked, withouth connecting to a running database server.

Is this what you're asking?

Because.. with sqlite in RAM you _ARE_ using the whole stack of the
database, only there is no separate server process.

Ben Finney wrote:

I'm not sure I understand.
You cannot connect to postgres and use all of the postgres features,
like you asked, withouth connecting to a running database server.

Is this what you're asking?

Because.. with sqlite in RAM you _ARE_ using the whole stack of the
database, only there is no separate server process.

Ben Finney wrote:

I'm not sure I understand.
You cannot connect to postgres and use all of the postgres features,
like you asked, withouth connecting to a running database server.

Is this what you're asking?

Because.. with sqlite in RAM you _ARE_ using the whole stack of the
database, only there is no separate server process.

Marco Mariani <marco (AT) sferacarta (DOT) com> writes:

Yes. I want to connect to a PostgreSQL database without the external
dependency of a cluster and already-running server.

And no filesystem interaction, and no concurrency, and many other
things that come with a "dedicated to this one process" database.

All of these make it very useful for unit testing a unit of code that
would, under normal operation, connect to the concurrent database with
its on-disk cluster and all the rest.

I'm wanting to have these advantages, but have it be PostgreSQL so
that I don't have to make an in-memory SQLite database pretend to be
an in-memory PostgreSQL one.

--
\ "Pinky, are you pondering what I'm pondering?" "I think so, |
`\ Brain, but if we give peas a chance, won't the lima beans feel |
_o__) left out?" -- _Pinky and The Brain_ |
Ben Finney