| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Florian Wunderlich <fwunderlich(at)devbrain(dot)de> |
| Cc: | pgsql-bugs(at)postgresql(dot)org, pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: Bug #866 related problem (ATTN Tom Lane) |
| Date: | 2003-02-12 23:27:01 |
| Message-ID: | 8579.1045092421@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-docs |
Florian Wunderlich <fwunderlich(at)devbrain(dot)de> writes:
> So can I be sure that every non-aggregate SELECT on tables joined with
> unique indexes works, independent of the WHERE or ORDER BY?
I would think that backwards scan on a join mostly doesn't work, but
haven't tried it in any detail.
A plan with a SORT node at the top *will* work, no matter what's under
the SORT, so ORDER BY might mask problems in some cases.
> Is anybody working on implementing this functionality?
Not me... although I have thought about at least adding enough code to
report an error in the cases that will give wrong answers.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-02-13 05:27:54 | Re: Constraints not check indexes existence on creation. |
| Previous Message | Bruno Wolff III | 2003-02-12 20:45:48 | Re: cvs (7/2/2003) broken? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florian Wunderlich | 2003-02-13 16:27:21 | Re: Bug #866 related problem (ATTN Tom Lane) |
| Previous Message | Wilson, Scott | 2003-02-12 20:54:44 | Row ordering difference in regression test output |