| From: | David Johnston <polobo(at)yahoo(dot)com> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #9896: Bug in FULL OUTER JOIN |
| Date: | 2014-04-07 17:43:17 |
| Message-ID: | 1396892597266-5799042.post@n5.nabble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Tom Lane-2 wrote
> In any case, don't hold your breath waiting for a fix; I'm just asking
> to gather information for possible future work. This is unlikely to
> be simple to fix, and it's not going to be very high on anyone's priority
> list either, given that few people use FULL JOIN as far as I've heard.
Infrequently, maybe, but especially for dataset comparisons FULL JOIN is
convenient. That said, typically reformulation of the data and/or query is
possible, even if somewhat slower, so it isn't like getting a result is
impossible given this limitation.
David J.
--
View this message in context: http://postgresql.1045698.n5.nabble.com/BUG-9896-Bug-in-FULL-OUTER-JOIN-tp5799008p5799042.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | klimm | 2014-04-07 18:09:53 | BUG #9897: Wrong Julian Date through ODBC |
| Previous Message | Tom Lane | 2014-04-07 16:34:36 | Re: Postgres resources not released after call PQclear |