pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedLack of detailed documentation
11+ messages / 4 participants
[nested] [flat]
* Lack of detailed documentation
@ 2020-02-07 21:12 PG Doc comments form <noreply@postgresql.org>
2020-02-08 20:32 ` Re: Lack of detailed documentation David G. Johnston <david.g.johnston@gmail.com>
0 siblings, 1 reply; 11+ messages in thread
From: PG Doc comments form @ 2020-02-07 21:12 UTC (permalink / raw)
To: pgsql-docs@lists.postgresql.org; +Cc: randolph.a.strauss@nasa.gov
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/12/functions-geometry.html
Description:
On: https://www.postgresql.org/docs/current/functions-geometry.html
The functions aren't defined, nor have pointers. For instance:
* Scaling/rotation box '((0,0),(1,1))' * point '(2.0,0)'
I see how it can be scaling (or shearing), but how does it do rotation?
Or maybe when the points x^2+y^2 == 1, it's interpreted at rotation?
Each operator needs a full explanation...
thx
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Lack of detailed documentation
2020-02-07 21:12 Lack of detailed documentation PG Doc comments form <noreply@postgresql.org>
@ 2020-02-08 20:32 ` David G. Johnston <david.g.johnston@gmail.com>
2020-02-09 16:08 ` Re: Lack of detailed documentation Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 11+ messages in thread
From: David G. Johnston @ 2020-02-08 20:32 UTC (permalink / raw)
To: randolph.a.strauss@nasa.gov; pgsql-docs@lists.postgresql.org
On Fri, Feb 7, 2020 at 4:53 PM PG Doc comments form <noreply@postgresql.org>
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/12/functions-geometry.html
> Description:
>
> On: https://www.postgresql.org/docs/current/functions-geometry.html
>
> The functions aren't defined, nor have pointers. For instance:
> * Scaling/rotation box '((0,0),(1,1))' * point '(2.0,0)'
>
> I see how it can be scaling (or shearing), but how does it do rotation?
> Or maybe when the points x^2+y^2 == 1, it's interpreted at rotation?
>
Google: "box point multiplication postgres" came up with the follow book
section:
https://books.google.com/books?id=gkQVL9pyFVYC&pg=PA95&lpg=PA95&dq=box+point+multiplicat...
Haven't independently confirm the math but it sounds reasonable...
Each operator needs a full explanation...
>
Patch submissions are welcomed.
David J.
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Lack of detailed documentation
2020-02-07 21:12 Lack of detailed documentation PG Doc comments form <noreply@postgresql.org>
2020-02-08 20:32 ` Re: Lack of detailed documentation David G. Johnston <david.g.johnston@gmail.com>
@ 2020-02-09 16:08 ` Tom Lane <tgl@sss.pgh.pa.us>
2020-02-10 18:39 ` Re: [EXTERNAL] Re: Lack of detailed documentation Strauss, Randy (ARC-AF)[SGT, INC] <randolph.a.strauss@nasa.gov>
0 siblings, 1 reply; 11+ messages in thread
From: Tom Lane @ 2020-02-09 16:08 UTC (permalink / raw)
To: David G. Johnston <david.g.johnston@gmail.com>; +Cc: randolph.a.strauss@nasa.gov; pgsql-docs@lists.postgresql.org
"David G. Johnston" <david.g.johnston@gmail.com> writes:
> On Fri, Feb 7, 2020 at 4:53 PM PG Doc comments form <noreply@postgresql.org>
> wrote:
>> On: https://www.postgresql.org/docs/current/functions-geometry.html
>> The functions aren't defined, nor have pointers. For instance:
>> * Scaling/rotation box '((0,0),(1,1))' * point '(2.0,0)'
>> I see how it can be scaling (or shearing), but how does it do rotation?
>> Or maybe when the points x^2+y^2 == 1, it's interpreted at rotation?
> Google: "box point multiplication postgres" came up with the follow book
> section:
> Haven't independently confirm the math but it sounds reasonable...
I responded to the OP about this but unaccountably forgot to cc the list.
The two main points were:
* Per high-school-level vector geometry, rotation around the origin
by an angle theta is equivalent to multiplying by the vector
(cos(theta), sin(theta)). (So no, the book section you quoted isn't
quite right :-(.) But we can't go and offer a geometry course on
this page.
* While this works for rotating points, paths, and circles, it
doesn't really work for rotating boxes, because for any rotation
angle that's not a multiple of 90 degrees, you'd need to end up with
a tilted box ... and our box type has no notion of tilted. The
specified corners rotate to the right places, but the box size isn't
preserved.
So it seems fairly unfortunate to me that the two examples of
scaling/rotation use a box as the LHS. I could get behind changing
them to use, say, a path as LHS. But I don't think there's room to
explain how to do rotation if you don't know that already, any more
than (say) our explanation of aggregate functions tries to explain
statistics.
regards, tom lane
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: [EXTERNAL] Re: Lack of detailed documentation
2020-02-07 21:12 Lack of detailed documentation PG Doc comments form <noreply@postgresql.org>
2020-02-08 20:32 ` Re: Lack of detailed documentation David G. Johnston <david.g.johnston@gmail.com>
2020-02-09 16:08 ` Re: Lack of detailed documentation Tom Lane <tgl@sss.pgh.pa.us>
@ 2020-02-10 18:39 ` Strauss, Randy (ARC-AF)[SGT, INC] <randolph.a.strauss@nasa.gov>
2020-02-10 19:41 ` Re: Lack of detailed documentation David G. Johnston <david.g.johnston@gmail.com>
0 siblings, 1 reply; 11+ messages in thread
From: Strauss, Randy (ARC-AF)[SGT, INC] @ 2020-02-10 18:39 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; David G. Johnston <david.g.johnston@gmail.com>; +Cc: pgsql-docs@lists.postgresql.org <pgsql-docs@lists.postgresql.org>
Yes, I figured this out. People shouldn't have to figure out that the 2 numbers in the vector are the scale and rotation.
They could be the rotation and scale. The rotation could be in degrees or radians.
This is documentation- it should explain it.
And yes, does it rotate around its center, or the origin?
And this was just one example. Every friggin' one of them needs to be documented.
I'm not demanding that they be done right away, but there should be a description of each. They can all start with TBD...
-r
Randy Strauss, desk: 650-604-0431 (Bldg N210, Rm 145, Cube 36)
On 2/9/20, 8:09 AM, "Tom Lane" <tgl@sss.pgh.pa.us> wrote:
"David G. Johnston" <david.g.johnston@gmail.com> writes:
> On Fri, Feb 7, 2020 at 4:53 PM PG Doc comments form <noreply@postgresql.org>
> wrote:
>> On: https://urldefense.proofpoint.com/v2/url?u=https-3A__www.postgresql.org_docs_current_functions-2Dgeo...
>> The functions aren't defined, nor have pointers. For instance:
>> * Scaling/rotation box '((0,0),(1,1))' * point '(2.0,0)'
>> I see how it can be scaling (or shearing), but how does it do rotation?
>> Or maybe when the points x^2+y^2 == 1, it's interpreted at rotation?
> Google: "box point multiplication postgres" came up with the follow book
> section:
> Haven't independently confirm the math but it sounds reasonable...
I responded to the OP about this but unaccountably forgot to cc the list.
The two main points were:
* Per high-school-level vector geometry, rotation around the origin
by an angle theta is equivalent to multiplying by the vector
(cos(theta), sin(theta)). (So no, the book section you quoted isn't
quite right :-(.) But we can't go and offer a geometry course on
this page.
* While this works for rotating points, paths, and circles, it
doesn't really work for rotating boxes, because for any rotation
angle that's not a multiple of 90 degrees, you'd need to end up with
a tilted box ... and our box type has no notion of tilted. The
specified corners rotate to the right places, but the box size isn't
preserved.
So it seems fairly unfortunate to me that the two examples of
scaling/rotation use a box as the LHS. I could get behind changing
them to use, say, a path as LHS. But I don't think there's room to
explain how to do rotation if you don't know that already, any more
than (say) our explanation of aggregate functions tries to explain
statistics.
regards, tom lane
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Lack of detailed documentation
2020-02-07 21:12 Lack of detailed documentation PG Doc comments form <noreply@postgresql.org>
2020-02-08 20:32 ` Re: Lack of detailed documentation David G. Johnston <david.g.johnston@gmail.com>
2020-02-09 16:08 ` Re: Lack of detailed documentation Tom Lane <tgl@sss.pgh.pa.us>
2020-02-10 18:39 ` Re: [EXTERNAL] Re: Lack of detailed documentation Strauss, Randy (ARC-AF)[SGT, INC] <randolph.a.strauss@nasa.gov>
@ 2020-02-10 19:41 ` David G. Johnston <david.g.johnston@gmail.com>
2020-02-10 20:43 ` Re: Lack of detailed documentation Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 11+ messages in thread
From: David G. Johnston @ 2020-02-10 19:41 UTC (permalink / raw)
To: Strauss, Randy (ARC-AF)[SGT, INC] <randolph.a.strauss@nasa.gov>; +Cc: Tom Lane <tgl@sss.pgh.pa.us>; pgsql-docs@lists.postgresql.org <pgsql-docs@lists.postgresql.org>
On Monday, February 10, 2020, Strauss, Randy (ARC-AF)[SGT, INC] <
randolph.a.strauss@nasa.gov> wrote:
> Yes, I figured this out. People shouldn't have to figure out that the 2
> numbers in the vector are the scale and rotation.
> They could be the rotation and scale. The rotation could be in degrees or
> radians.
> This is documentation- it should explain it.
> And yes, does it rotate around its center, or the origin?
> And this was just one example. Every friggin' one of them needs to be
> documented.
> I'm not demanding that they be done right away, but there should be a
> description of each. They can all start with TBD...
>
I doubt anyone disagrees with the sentiment but the last time the lack of
documentation was brought up here was years ago and no one stepped up then
to volunteer their time to improve this lesser used area of the database
and it doesn’t seem likely to happen organically here either as this
message seems to imply a lack of interest in being part of the solution.
David J.
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Lack of detailed documentation
2020-02-07 21:12 Lack of detailed documentation PG Doc comments form <noreply@postgresql.org>
2020-02-08 20:32 ` Re: Lack of detailed documentation David G. Johnston <david.g.johnston@gmail.com>
2020-02-09 16:08 ` Re: Lack of detailed documentation Tom Lane <tgl@sss.pgh.pa.us>
2020-02-10 18:39 ` Re: [EXTERNAL] Re: Lack of detailed documentation Strauss, Randy (ARC-AF)[SGT, INC] <randolph.a.strauss@nasa.gov>
2020-02-10 19:41 ` Re: Lack of detailed documentation David G. Johnston <david.g.johnston@gmail.com>
@ 2020-02-10 20:43 ` Tom Lane <tgl@sss.pgh.pa.us>
2020-04-22 23:36 ` Re: Lack of detailed documentation Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 11+ messages in thread
From: Tom Lane @ 2020-02-10 20:43 UTC (permalink / raw)
To: David G. Johnston <david.g.johnston@gmail.com>; +Cc: Strauss, Randy (ARC-AF)[SGT, INC] <randolph.a.strauss@nasa.gov>; pgsql-docs@lists.postgresql.org <pgsql-docs@lists.postgresql.org>
"David G. Johnston" <david.g.johnston@gmail.com> writes:
> I doubt anyone disagrees with the sentiment but the last time the lack of
> documentation was brought up here was years ago and no one stepped up then
> to volunteer their time to improve this lesser used area of the database
> and it doesn't seem likely to happen organically here either as this
> message seems to imply a lack of interest in being part of the solution.
Yeah. Attached is my proposal for clarifying what to do to rotate.
There's a lot more that could be done to improve this page --- for
one thing, most of the other similar tables show the results of the
examples, and for another, it's pretty unclear which data types
each operator takes. But I don't have the time or interest to
tackle a major rewrite, and so far nobody else has stepped up either.
One thing that's sort of blocking any real progress on this is the
draconian space constraints imposed by the tabular format, which is
hurting us on a lot of these pages, not just this one. Alvaro did
some preliminary investigation towards finding a better way [1],
but nobody's tried to push that forward.
regards, tom lane
[1] https://www.postgresql.org/message-id/20200116184444.GA25792%40alvherre.pgsql
Attachments:
[text/x-diff] better-geometry-rotation-examples.patch (1.1K, ../../27125.1581367420@sss.pgh.pa.us/2-better-geometry-rotation-examples.patch)
download | inline diff:
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index ceda48e..400b21d 100644
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -8363,12 +8363,18 @@ CREATE TYPE rainbow AS ENUM ('red', 'orange', 'yellow', 'green', 'blue', 'purple
<row>
<entry> <literal>*</literal> </entry>
<entry>Scaling/rotation</entry>
- <entry><literal>box '((0,0),(1,1))' * point '(2.0,0)'</literal></entry>
+ <entry>
+ <para><literal>path '(0,0),(1,0),(1,1)' * point '(3.0,0)'</literal></para>
+ <para><literal>path '(0,0),(1,0),(1,1)' * point(cosd(45), sind(45))</literal></para>
+ </entry>
</row>
<row>
<entry> <literal>/</literal> </entry>
<entry>Scaling/rotation</entry>
- <entry><literal>box '((0,0),(2,2))' / point '(2.0,0)'</literal></entry>
+ <entry>
+ <para><literal>path '(0,0),(1,0),(1,1)' / point '(2.0,0)'</literal></para>
+ <para><literal>path '(0,0),(1,0),(1,1)' / point(cosd(45), sind(45))</literal></para>
+ </entry>
</row>
<row>
<entry> <literal>#</literal> </entry>
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Lack of detailed documentation
2020-02-07 21:12 Lack of detailed documentation PG Doc comments form <noreply@postgresql.org>
2020-02-08 20:32 ` Re: Lack of detailed documentation David G. Johnston <david.g.johnston@gmail.com>
2020-02-09 16:08 ` Re: Lack of detailed documentation Tom Lane <tgl@sss.pgh.pa.us>
2020-02-10 18:39 ` Re: [EXTERNAL] Re: Lack of detailed documentation Strauss, Randy (ARC-AF)[SGT, INC] <randolph.a.strauss@nasa.gov>
2020-02-10 19:41 ` Re: Lack of detailed documentation David G. Johnston <david.g.johnston@gmail.com>
2020-02-10 20:43 ` Re: Lack of detailed documentation Tom Lane <tgl@sss.pgh.pa.us>
@ 2020-04-22 23:36 ` Tom Lane <tgl@sss.pgh.pa.us>
2020-04-23 00:18 ` Re: Lack of detailed documentation David G. Johnston <david.g.johnston@gmail.com>
2020-04-23 00:31 ` Re: Lack of detailed documentation David G. Johnston <david.g.johnston@gmail.com>
0 siblings, 2 replies; 11+ messages in thread
From: Tom Lane @ 2020-04-22 23:36 UTC (permalink / raw)
To: David G. Johnston <david.g.johnston@gmail.com>; +Cc: Strauss, Randy (ARC-AF)[SGT, INC] <randolph.a.strauss@nasa.gov>; pgsql-docs@lists.postgresql.org <pgsql-docs@lists.postgresql.org>
I wrote:
> One thing that's sort of blocking any real progress on this is the
> draconian space constraints imposed by the tabular format, which is
> hurting us on a lot of these pages, not just this one. Alvaro did
> some preliminary investigation towards finding a better way,
> but nobody's tried to push that forward.
I've been making an attempt to improve that situation, and along
the way just pushed an expansion of the geometric-operator docs:
https://www.postgresql.org/docs/devel/functions-geometry.html
There's probably still some things to be desired, but it's a lot
less fuzzy than before.
One thing that surprised me is that I couldn't find any well-known
name for what the * and / operators are doing; digging around on
the net and in some dusty old math textbooks didn't yield any exact
matches. I ended up adding footnotes with the actual computations,
but I'm not very happy with that approach. Surely Lockhart[1] got this
definition from someplace, though, and didn't invent it out of thin air.
regards, tom lane
[1] I'd supposed we could blame this stuff on Berkeley, but excavation
in our git history shows it came in at
https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=9e2a87b62db87fc4175b00dab...
... sans documentation of course.
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Lack of detailed documentation
2020-02-07 21:12 Lack of detailed documentation PG Doc comments form <noreply@postgresql.org>
2020-02-08 20:32 ` Re: Lack of detailed documentation David G. Johnston <david.g.johnston@gmail.com>
2020-02-09 16:08 ` Re: Lack of detailed documentation Tom Lane <tgl@sss.pgh.pa.us>
2020-02-10 18:39 ` Re: [EXTERNAL] Re: Lack of detailed documentation Strauss, Randy (ARC-AF)[SGT, INC] <randolph.a.strauss@nasa.gov>
2020-02-10 19:41 ` Re: Lack of detailed documentation David G. Johnston <david.g.johnston@gmail.com>
2020-02-10 20:43 ` Re: Lack of detailed documentation Tom Lane <tgl@sss.pgh.pa.us>
2020-04-22 23:36 ` Re: Lack of detailed documentation Tom Lane <tgl@sss.pgh.pa.us>
@ 2020-04-23 00:18 ` David G. Johnston <david.g.johnston@gmail.com>
2020-04-23 00:22 ` Re: Lack of detailed documentation David G. Johnston <david.g.johnston@gmail.com>
1 sibling, 1 reply; 11+ messages in thread
From: David G. Johnston @ 2020-04-23 00:18 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Strauss, Randy (ARC-AF)[SGT, INC] <randolph.a.strauss@nasa.gov>; pgsql-docs@lists.postgresql.org <pgsql-docs@lists.postgresql.org>
On Wed, Apr 22, 2020 at 4:36 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> One thing that surprised me is that I couldn't find any well-known
> name for what the * and / operators are doing; digging around on
> the net and in some dusty old math textbooks didn't yield any exact
> matches. I ended up adding footnotes with the actual computations,
> but I'm not very happy with that approach. Surely Lockhart[1] got this
> definition from someplace, though, and didn't invent it out of thin air.
>
>
I'd move the footnote indicator to:
Available for point[a], box, path, circle.
Available for point[b], box, path, circle.
As the footnote only applies to that specific left operand type.
Or maybe:
Available for box, path, and circle. It is also defined for point [a] but
it has no related physical meaning.
David J.
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Lack of detailed documentation
2020-02-07 21:12 Lack of detailed documentation PG Doc comments form <noreply@postgresql.org>
2020-02-08 20:32 ` Re: Lack of detailed documentation David G. Johnston <david.g.johnston@gmail.com>
2020-02-09 16:08 ` Re: Lack of detailed documentation Tom Lane <tgl@sss.pgh.pa.us>
2020-02-10 18:39 ` Re: [EXTERNAL] Re: Lack of detailed documentation Strauss, Randy (ARC-AF)[SGT, INC] <randolph.a.strauss@nasa.gov>
2020-02-10 19:41 ` Re: Lack of detailed documentation David G. Johnston <david.g.johnston@gmail.com>
2020-02-10 20:43 ` Re: Lack of detailed documentation Tom Lane <tgl@sss.pgh.pa.us>
2020-04-22 23:36 ` Re: Lack of detailed documentation Tom Lane <tgl@sss.pgh.pa.us>
2020-04-23 00:18 ` Re: Lack of detailed documentation David G. Johnston <david.g.johnston@gmail.com>
@ 2020-04-23 00:22 ` David G. Johnston <david.g.johnston@gmail.com>
0 siblings, 0 replies; 11+ messages in thread
From: David G. Johnston @ 2020-04-23 00:22 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Strauss, Randy (ARC-AF)[SGT, INC] <randolph.a.strauss@nasa.gov>; pgsql-docs@lists.postgresql.org <pgsql-docs@lists.postgresql.org>
On Wed, Apr 22, 2020 at 5:18 PM David G. Johnston <
david.g.johnston@gmail.com> wrote:
> On Wed, Apr 22, 2020 at 4:36 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
>> One thing that surprised me is that I couldn't find any well-known
>> name for what the * and / operators are doing; digging around on
>> the net and in some dusty old math textbooks didn't yield any exact
>> matches. I ended up adding footnotes with the actual computations,
>> but I'm not very happy with that approach. Surely Lockhart[1] got this
>> definition from someplace, though, and didn't invent it out of thin air.
>>
>>
> I'd move the footnote indicator to:
>
> Available for point[a], box, path, circle.
> Available for point[b], box, path, circle.
>
> As the footnote only applies to that specific left operand type.
>
> Or maybe:
>
> Available for box, path, and circle. It is also defined for point [a] but
> it has no related physical meaning.
>
Nevermind...
David J.
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Lack of detailed documentation
2020-02-07 21:12 Lack of detailed documentation PG Doc comments form <noreply@postgresql.org>
2020-02-08 20:32 ` Re: Lack of detailed documentation David G. Johnston <david.g.johnston@gmail.com>
2020-02-09 16:08 ` Re: Lack of detailed documentation Tom Lane <tgl@sss.pgh.pa.us>
2020-02-10 18:39 ` Re: [EXTERNAL] Re: Lack of detailed documentation Strauss, Randy (ARC-AF)[SGT, INC] <randolph.a.strauss@nasa.gov>
2020-02-10 19:41 ` Re: Lack of detailed documentation David G. Johnston <david.g.johnston@gmail.com>
2020-02-10 20:43 ` Re: Lack of detailed documentation Tom Lane <tgl@sss.pgh.pa.us>
2020-04-22 23:36 ` Re: Lack of detailed documentation Tom Lane <tgl@sss.pgh.pa.us>
@ 2020-04-23 00:31 ` David G. Johnston <david.g.johnston@gmail.com>
2020-04-23 00:47 ` Re: Lack of detailed documentation Tom Lane <tgl@sss.pgh.pa.us>
1 sibling, 1 reply; 11+ messages in thread
From: David G. Johnston @ 2020-04-23 00:31 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Strauss, Randy (ARC-AF)[SGT, INC] <randolph.a.strauss@nasa.gov>; pgsql-docs@lists.postgresql.org <pgsql-docs@lists.postgresql.org>
On Wed, Apr 22, 2020 at 4:36 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Surely Lockhart[1] got this
> definition from someplace, though, and didn't invent it out of thin air.
>
I actually viewed quite a few YouTube math videos between then and now and
looking at it now it seems familiar.
It is basically treating the points as if they were a representation of
complex numbers with x being real and y being imaginary.
https://en.wikipedia.org/wiki/Complex_number (Multiplication and Division
sections)
David J.
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Lack of detailed documentation
2020-02-07 21:12 Lack of detailed documentation PG Doc comments form <noreply@postgresql.org>
2020-02-08 20:32 ` Re: Lack of detailed documentation David G. Johnston <david.g.johnston@gmail.com>
2020-02-09 16:08 ` Re: Lack of detailed documentation Tom Lane <tgl@sss.pgh.pa.us>
2020-02-10 18:39 ` Re: [EXTERNAL] Re: Lack of detailed documentation Strauss, Randy (ARC-AF)[SGT, INC] <randolph.a.strauss@nasa.gov>
2020-02-10 19:41 ` Re: Lack of detailed documentation David G. Johnston <david.g.johnston@gmail.com>
2020-02-10 20:43 ` Re: Lack of detailed documentation Tom Lane <tgl@sss.pgh.pa.us>
2020-04-22 23:36 ` Re: Lack of detailed documentation Tom Lane <tgl@sss.pgh.pa.us>
2020-04-23 00:31 ` Re: Lack of detailed documentation David G. Johnston <david.g.johnston@gmail.com>
@ 2020-04-23 00:47 ` Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 11+ messages in thread
From: Tom Lane @ 2020-04-23 00:47 UTC (permalink / raw)
To: David G. Johnston <david.g.johnston@gmail.com>; +Cc: Strauss, Randy (ARC-AF)[SGT, INC] <randolph.a.strauss@nasa.gov>; pgsql-docs@lists.postgresql.org <pgsql-docs@lists.postgresql.org>
"David G. Johnston" <david.g.johnston@gmail.com> writes:
> It is basically treating the points as if they were a representation of
> complex numbers with x being real and y being imaginary.
Hah! I was too focused on looking for definitions involving vectors,
and didn't think of plain ol' complex numbers. But yes, that's exactly
what it is. I'll go improve the docs.
regards, tom lane
^ permalink raw reply [nested|flat] 11+ messages in thread
end of thread, other threads:[~2020-04-23 00:47 UTC | newest]
Thread overview: 11+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2020-02-07 21:12 Lack of detailed documentation PG Doc comments form <noreply@postgresql.org>
2020-02-08 20:32 ` David G. Johnston <david.g.johnston@gmail.com>
2020-02-09 16:08 ` Tom Lane <tgl@sss.pgh.pa.us>
2020-02-10 18:39 ` Strauss, Randy (ARC-AF)[SGT, INC] <randolph.a.strauss@nasa.gov>
2020-02-10 19:41 ` David G. Johnston <david.g.johnston@gmail.com>
2020-02-10 20:43 ` Tom Lane <tgl@sss.pgh.pa.us>
2020-04-22 23:36 ` Tom Lane <tgl@sss.pgh.pa.us>
2020-04-23 00:18 ` David G. Johnston <david.g.johnston@gmail.com>
2020-04-23 00:22 ` David G. Johnston <david.g.johnston@gmail.com>
2020-04-23 00:31 ` David G. Johnston <david.g.johnston@gmail.com>
2020-04-23 00:47 ` Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox