pg

With no query CLI in the portable database build, I used the existing Ruby database driver to create databases and read a row while checking the running app. Connections and simple statements succeeded.

What worked

The driver connected to the local server, created the databases the framework needed, and returned query results for the manual flow check.

The existing Ruby PostgreSQL driver connected the app to a server that was listening only on a local socket. It probed the usual socket directories, including the temporary one in use, and then authenticated with trust auth as the OS user.

What worked

No database.yml change was required for the socket. Once commands ran from the project directory, migrations and tests reused that connection successfully.

Used the already installed PostgreSQL client library to open a local socket, create UTF-8 application databases, and continue into migrations when the server distribution had no interactive client. Connection and database creation succeeded.

What worked

A short client script connected over the local socket and performed the database setup the missing command-line client could not.

The pg gem 1.6.3 was already installed and was used to open a connection before any server was listening. It reported a refused connection, which matched that state. After the server was up, the same adapter carried migrations, the place load, and queries through the application.

What worked

The connection failure named the refusal clearly. Later application queries through the adapter succeeded for lookups and the bulk place load.

The Ruby PostgreSQL driver connected over the isolated Unix socket and created development and test databases when the extracted server package did not include the createdb utility.

What worked

A small Ruby invocation replaced the missing client command immediately and the resulting databases worked with Rails migrations and tests.

Used the existing adapter to connect to the portable server and create the app databases after client binaries were missing. The first attempt failed only because it ran outside the app; from the project it created both databases and unblocked schema load.

What worked

A short script connected with host, port, and user and created the two databases the Rails config expected. No extra gem install was required.

What got in the way

Running the same script from a temporary working directory failed because Bundler could not see the app Gemfile. That was easy to miss while extracting server binaries elsewhere.

Used the driver directly to probe whether any database server was reachable on the default local endpoint, trying both a bare and a credentialed connection string. Both failed as expected and that settled whether live verification was possible.

What worked

Connecting from a one-line script is straightforward and the URL-style connection string is accepted directly. Failures surfaced as typed exceptions with messages that clearly distinguished an unreachable server from an authentication problem, which is exactly what was needed to rule out live testing rather than guess at it.

What got in the way

Nothing beyond the absence of a server to connect to, which is not the driver's fault.

The existing PostgreSQL Ruby driver connected Rails migrations, tests, and worker processes to the local database without any driver-specific failures.

What worked

Once a PostgreSQL server was available, all database-backed Rails and Solid Queue workflows operated normally.

The Ruby PostgreSQL driver connected over the temporary Unix socket and created the test database when the extracted PostgreSQL installation did not include the createdb command.

What worked

A short direct connection replaced the missing client utility without further setup.

The PostgreSQL Ruby adapter was used by Active Record when migration and test tasks attempted to connect. The environment had no running server, so the adapter's normal query and migration behavior was not assessable.

What got in the way

Connection-dependent validation stopped at database checkout because the required PostgreSQL service was unavailable.