pg.ddx.io  pgpartman/pg_partman GitHub issues and pull requests  
help / color / mirror / Atom feed
From: TanelPauls (@TanelPauls) <noreply+TanelPauls@github.com>
To: pgpartman/pg_partman <noreply+pgpartman-pg_partman@github.com>
Subject: [pgpartman/pg_partman] issue #891: pg_partman_bgw fails on PostgreSQL 18.7: cannot drop portal "<unnamed portal 1>" while it is being set up
Date: Tue, 17 Nov 2026 14:12:04 +0000
Message-ID: <gh-pgpartman-pg_partman-891@github.com> (raw)

After upgrading to PostgreSQL 18.7, the background worker fails on every run. Calling the maintenance procedure manually still works.

### Environment
- PostgreSQL 18.7 (Debian 18.7-1.pgdg13+2), official `postgres:18.7` Docker image (Debian trixie)
- pg_partman 5.5.0, apt package `postgresql-18-partman` 5.5.0-1.pgdg13+2 (from apt.postgresql.org)

### Steps to reproduce
```dockerfile
FROM postgres:18.7
RUN apt-get update && apt-get install -y postgresql-18-partman
```
```sh
docker run -d --name repro -e POSTGRES_PASSWORD=x <image> \
  -c shared_preload_libraries=pg_partman_bgw \
  -c pg_partman_bgw.dbname=postgres \
  -c pg_partman_bgw.role=postgres \
  -c pg_partman_bgw.interval=10
```
```sql
CREATE SCHEMA partman;
CREATE EXTENSION pg_partman SCHEMA partman;
CREATE TABLE public.events (id bigint, created_at timestamptz NOT NULL) PARTITION BY RANGE (created_at);
SELECT partman.create_parent('public.events', 'created_at', '1 day');
```

### Actual
On every interval:
```
ERROR:  cannot drop portal "<unnamed portal 1>" while it is being set up
LOG:  background worker "pg_partman background worker" (PID 91) exited with exit code 1
```

### Expected
The worker runs `run_maintenance_proc()` without errors, as it does on 18.6.

### Notes
- The same setup on PostgreSQL 18.6 with `postgresql-18-partman` 5.5.0-1.pgdg13+1 runs with no errors.
- Running `CALL partman.run_maintenance_proc();` or `SELECT partman.run_maintenance();` by hand on 18.7 works.
- This is probably related to the 18.7 change "Disallow closing a portal that is still being set up" (CVE-2026-116332). The worker sets up its own portal and then calls `run_maintenance_proc()` non-atomically through `SPI_execute_extended` (`src/pg_partman_bgw.c`, around lines 419–427 and 499–507). The COMMIT inside the procedure appears to trip the new check.
- Side note for packagers: `5.5.0-1.pgdg13+2` depends on `postgresql-18 (>> 18.7)`, so installing it on an 18.6 image quietly upgrades the server to 18.7.


view thread (12+ messages)  latest in thread

Message-ID: <gh-pgpartman-pg_partman-891@github.com>
Permalink:  ../gh-pgpartman-pg_partman-891@github.com/

 · 


This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox