Bump pytest-postgresql from 8.1.0 to 9.0.0

[dependabot]

Bumps pytest-postgresql from 8.1.0 to 9.0.0.

Changelog

Sourced from pytest-postgresql's changelog.

pytest-postgresql 9.0.0 (2026-08-28)

Breaking changes

• Load functions passed to proc/noproc fixtures have to accept new autocommit argument. ([#902](https://github.com/dbfixtures/pytest-postgresql/issues/902) <https://github.com/dbfixtures/pytest-postgresql/issues/902>__)
• postgresql_noproc has an additional parameter load_autocommit which is grouped together with load making positional arguments filled till depends_on incompatible. ([#902](https://github.com/dbfixtures/pytest-postgresql/issues/902) <https://github.com/dbfixtures/pytest-postgresql/issues/902>__)
• Arguments after dbname in postgresql_noproc are now keyword-only. Update callers that pass options, load, load_autocommit or depends_on positionally. ([#1387](https://github.com/dbfixtures/pytest-postgresql/issues/1387) <https://github.com/dbfixtures/pytest-postgresql/issues/1387>__)
• Arguments after dbname in postgresql_proc are now keyword-only. Update callers that pass options, startparams, unixsocketdir, postgres_options, load or load_autocommit positionally. ([#1387](https://github.com/dbfixtures/pytest-postgresql/issues/1387) <https://github.com/dbfixtures/pytest-postgresql/issues/1387>__)
• Arguments after dbname in PostgreSQLExecutor. Update callers that pass +shell, timeout, sleep, user, password, +options, or postgres_options positionally. ([#1387](https://github.com/dbfixtures/pytest-postgresql/issues/1387) <https://github.com/dbfixtures/pytest-postgresql/issues/1387>__)

Deprecations

• Deprecated the unused version argument of DatabaseJanitor and AsyncDatabaseJanitor. ([#1393](https://github.com/dbfixtures/pytest-postgresql/issues/1393) <https://github.com/dbfixtures/pytest-postgresql/issues/1393>__)

Features

• The database used to create/drop test databases and read the server version is no longer hardcoded to postgres. Set it with the postgresql_maintenance_dbname ini option, the --postgresql-maintenance-dbname command line option, or the maintenance_dbname argument of factories.postgresql_noproc and DatabaseJanitor/AsyncDatabaseJanitor. Defaults to postgres. ([#653](https://github.com/dbfixtures/pytest-postgresql/issues/653) <https://github.com/dbfixtures/pytest-postgresql/issues/653>__)
• Allow running the SQL loader connection with autocommit enabled, so .sql files containing statements that cannot run inside a transaction block (such as CREATE DATABASE) can be loaded. This is configurable without a custom loader in three ways: the postgresql_load_autocommit ini option, the --postgresql-load-autocommit command line flag, or the load_autocommit argument of the postgresql_proc / postgresql_noproc factories (which also maps to an autocommit argument on DatabaseJanitor / AsyncDatabaseJanitor). ([#902](https://github.com/dbfixtures/pytest-postgresql/issues/902) <https://github.com/dbfixtures/pytest-postgresql/issues/902>__)
• Added async PostgreSQL fixture support via postgresql_async factory and AsyncDatabaseJanitor. Added optional async extra (pip install pytest-postgresql[async]) providing pytest-asyncio (>= 1.4) and aiofiles dependencies. ([#1235](https://github.com/dbfixtures/pytest-postgresql/issues/1235) <https://github.com/dbfixtures/pytest-postgresql/issues/1235>__)

Bugfixes

• pg_ctl discovery no longer hands back a path that does not exist. A client-only PostgreSQL install (Debian/Ubuntu's libpq-dev without the matching server package) makes pg_config --bindir point at a directory holding no pg_ctl; that path used to be returned unchecked, and the failure only surfaced later as Could not found ... when the executor read the server version. The path is now verified up front, and the ExecutableMissingException names the locations that were checked along with the ways to fix it: install the server package, point at a pg_ctl with --postgresql-exec, or use postgresql_noproc against a server you run yourself.

  A broken pg_config is reported the same way. Only FileNotFoundError used to be handled, so a non-executable or failing pg_config escaped as a raw PermissionError/CalledProcessError. ([#1031](https://github.com/dbfixtures/pytest-postgresql/issues/1031) <https://github.com/dbfixtures/pytest-postgresql/issues/1031>__)

• Fixed DeprecationWarning on Python 3.14 from deprecated asyncio event-loop policy usage on Windows; use pytest-asyncio loop factories instead. ([#1295](https://github.com/dbfixtures/pytest-postgresql/issues/1295) <https://github.com/dbfixtures/pytest-postgresql/issues/1295>__)

... (truncated)

Commits

• 9686bf0 Release 9.0.0
• f0dc05a Merge pull request #1431 from dbfixtures/issue-1397
• 89bb53b Enable PT ruff rulesets - closes #1397
• c529ae8 Merge pull request #1430 from dbfixtures/dependabot/github_actions/checkout-7...
• 73c82db Bump actions/checkout in the checkout group across 1 directory
• 2df6c20 Merge pull request #1429 from dbfixtures/issue-1402
• c5f74bb Gathered all executors under single executors package - closes #1402
• cf2522f Merge pull request #1428 from dbfixtures/issue-1423
• 0051aac Add actionlint to pre-commit - closes #1414
• 589c2a4 Merge pull request #1427 from dbfixtures/issue-1410
• Additional commits viewable in compare view

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 duplication

Metric	Results
Duplication	0

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}