| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Dickson S(dot) Guedes" <listas(at)guedesoft(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Analyzing bug 8049 |
| Date: | 2013-04-12 16:08:01 |
| Message-ID: | 19107.1365782881@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Dickson S. Guedes" <listas(at)guedesoft(dot)net> writes:
> In my tests, after ANALYZE _bug_header and _bug_line, the query plan
> changes and query results returns as expected. Is this a chance that
> things isn't too bad?
No, it just means that in this particular scenario, the bug only
manifests if a nestloop plan is chosen --- without that, there's no
possibility of pushing a join clause down to the scan level anyway.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2013-04-12 16:12:13 | Re: (auto)vacuum truncate exclusive lock |
| Previous Message | Andrew Dunstan | 2013-04-12 15:51:19 | Re: Detach/attach table and index data files from one cluster to another |