[PATCH] Report userid to PgBackendStatus for standalone backends
Hackorum builds and tests every patch posted to the lists, not only commitfest submissions. This is Hackorum's own CI rather than the PostgreSQL project's, and it is still under testing - please report anything that looks wrong.
You can run a PostgreSQL built from this patch straight from Docker, with no checkout and no build:
docker run --rm -p 5432:5432 ghcr.io/hackorum-dev/postgres-patch:t253708psql -h localhost -U postgresBuilt from patchset v1 (message #1), September 20, 2026 at 11:33 AM.
Every patchset is also pushed to a branch of our PostgreSQL fork, so you can check out the same tree CI built. Without a PostgreSQL checkout:
git clone --branch t253708_1 https://github.com/hackorum-dev/postgres.gitIn a checkout you already have, add the fork once:
git remote add hackorum https://github.com/hackorum-dev/postgres.gitthen, for this patchset and every later one:
git fetch hackorum t253708_1 && git checkout t253708_1Patchset v1 (message #1) is on t253708_1
Hi,
Standalone backends always use the BOOTSTRAP_SUPERUSER, it might be
good to report it to PgBackendStatus so that we can query it even in single
user mode.
Thoughts?
--
Regards,
ChangAo Chen
On Tue, Sep 08, 2026 at 06:02:52PM +0800, cca5507 wrote:
Standalone backends always use the BOOTSTRAP_SUPERUSER, it might be
good to report it to PgBackendStatus so that we can query it even in single
user mode.
Why should we care for a process kicked by postgres --single? No
other processes can look at the information provided. :)
--
Michael
Why should we care for a process kicked by postgres --single? No
other processes can look at the information provided. :)
Yeah, I find it by querying pg_stat_activity in single user mode and the result
doesn't show the username, which looks a bit strange though harmless.
--
Regards,
ChangAo Chen