Re: Doc patch on psql output formats
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Daniel Verite" <daniel@manitou-mail.org>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2018-11-06T15:03:14Z
Lists: pgsql-hackers
"Daniel Verite" <daniel@manitou-mail.org> writes: > psql's documentation has this mention about output formats: > "Unique abbreviations are allowed. (That would mean one letter is enough.)" > but "one letter is enough" is not true since 9.3 that added > "latex-longtable" sharing the same start as "latex", and then > 9.5 added "asciidoc" with the same first letter as "aligned". Yeah, that text has clearly outstayed its welcome. > When a non-unique abbreviation is used, psql uses the first > match in an arbitrary order defined in do_pset() by > a cascade of pg_strncasecmp(). Ugh. Should we not fix the code so that it complains if there's not a unique match? I would bet that the code was also written on the assumption that any abbrevation must be unique. regards, tom lane
Commits
-
Fix breakage of "\pset format latex".
- a7eece4fc9a4 12.0 landed
-
Make psql's "\pset format" command reject non-unique abbreviations.
- eaf746a5b85a 12.0 landed
-
Doc: remove claim that all \pset format options are unique in 1 letter.
- b8182d6293d9 11.2 landed
- 6a312b2587c6 9.4.21 landed
- 5f2937734cd1 10.7 landed
- 51eaaafb850b 12.0 landed
- 44dc82690d4e 9.5.16 landed
- 033d45a1008f 9.6.12 landed
-
Reorganize format options of psql in alphabetical order
- add9182e5908 12.0 cited