Re: BUG #4647: Geometric functions reorder their parameters randomly

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Juho Saarikko" <juho(dot)saarikko(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4647: Geometric functions reorder their parameters randomly
Date: 2009-02-12 17:04:32
Message-ID: 11573.1234458272@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Juho Saarikko" <juho(dot)saarikko(at)gmail(dot)com> writes:
> According to the online documentation, the ## operator is supposed to return
> "Closest point to first operand on second operand". However, in reality it
> seems to decide reorder its parameters as a function of them.

In the example you give, it looks like close_lseg (which close_sb
depends on) will sometimes return a point on its first argument
instead of its second one. If you think that the problem isn't
restricted to these two operators then you need to be more complete.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Heikki Linnakangas 2009-02-12 17:34:46 Re: BUG #4648: needless deadlock on tables having foreign-key
Previous Message Konstantin 2009-02-12 17:01:28 Re: BUG #4648: needless deadlock on tables having foreign-key