Doc patch on psql output formats

From: "Daniel Verite" <daniel(at)manitou-mail(dot)org>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Doc patch on psql output formats
Date: 2018-11-06 14:46:32
Message-ID: cb7e1caf-3ea6-450d-af28-f524903a030c@manitou-mail.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

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".

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().
(the recent commit add9182e reorders them alphabetically
but it turns out that it doesn't change the relative positions
of "aligned" / "asciidoc", or "latex" / "latex-longtables"
so \pset format a and \pset format l will continue to
select "aligned" and "latex" as before).

Anyway, "Unique abbreviations are allowed" deserves to
be changed as well.

PFA a doc patch to say simply "Abbreviations are allowed".

Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite

Attachment Content-Type Size
doc-psql-output-formats.patch text/plain 683 bytes

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-11-06 14:49:46 Re: plruby: rb_iterate symbol clash with libruby.so
Previous Message Andrew Gierth 2018-11-06 14:36:31 Re: Optimizing nested ConvertRowtypeExpr execution