| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | skalee(at)gmail(dot)com |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Chapter "8.8 Geometric Types" of documentation could contain more details |
| Date: | 2024-07-03 19:45:18 |
| Message-ID: | 3282371.1720035918@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
PG Doc comments form <noreply(at)postgresql(dot)org> writes:
> Hi, I am writing to suggest a couple of clarifications to "8.8. Geometric
> Types" documentation chapter.
Fair points. I am not really eager to say explicitly here that the
set of available functions varies for the different types: that seems
pretty self-evident. But your other ideas are good.
I also noted while looking at this that table 8.20 is flat out wrong
about the storage size of "line" values: they are 24 bytes each not
32. (This can be confirmed from pg_type.typlen or by looking at
struct LINE in the source code.)
How about the attached?
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| geometric-types-doc-improvement.patch | text/x-diff | 1.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-07-04 05:40:33 | Joe Hellerstein's "Looking Back at Postgres" paper |
| Previous Message | Daniel Gustafsson | 2024-07-03 16:51:57 | Re: Document when ssl_prefer_server_ciphers went in |