Move --interactive in createuser.sgml?
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:t77436psql -h localhost -U postgresBuilt from patchset v1 (message #1), September 20, 2026 at 10:48 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 t77436_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 t77436_1 && git checkout t77436_1Patchset v1 (message #1) is on t77436_1
Hello!
I noticed that the --interactive option in createuser.sgml is in the
list of short options rather than in the list of the long ones later on.
If it makes sense to move it below, the attached patch fixes that for
master (after --bypassrls/--no-bypassrls).
Please take a look.
--
Best regards,
Ekaterina Kiryanova
Technical Writer
Postgres Professional
the Russian PostgreSQL Company
On 4 Jul 2023, at 09:58, Ekaterina Kiryanova <e.kiryanova@postgrespro.ru> wrote:
I noticed that the --interactive option in createuser.sgml is in the list of short options rather than in the list of the long ones later on.
If it makes sense to move it below, the attached patch fixes that for master (after --bypassrls/--no-bypassrls).
Please take a look.
I'm not sure this moves the needle much in terms of consistency in listing
options, and I'm not sure there is policy to follow. createdb has long options
in alphabetical order, pg_basebackup has long options both by alphabetical and
grouped last, and pg_amcheck groups options by type.
Whether or not an option has a short option as well as a long option is an
implementation detail that I don't think should drive how we present the
information to the users in order to help them find what they need.
--
Daniel Gustafsson