| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Doc patch on psql output formats |
| Date: | 2018-11-06 15:03:14 |
| Message-ID: | 23366.1541516594@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Daniel Verite" <daniel(at)manitou-mail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2018-11-06 15:10:13 | Re: BUG #15212: Default values in partition tables don't work as expected and allow NOT NULL violation |
| Previous Message | Tom Lane | 2018-11-06 14:49:46 | Re: plruby: rb_iterate symbol clash with libruby.so |