| From: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
|---|---|
| To: | Ranjeet Dhumal <jeetu(dot)dhumal(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alban Hertroys <haramrae(at)gmail(dot)com>, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, Pgsql General list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: ERROR: volatile EquivalenceClass has no sortref |
| Date: | 2012-11-22 06:35:12 |
| Message-ID: | CABOikdNz2C8j8Gj_jFDmhnjnut_fVcu7pRN8kFJhuwhkcOGDpg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Thu, Nov 22, 2012 at 11:08 AM, Ranjeet Dhumal <jeetu(dot)dhumal(at)gmail(dot)com>wrote:
> Hi Tom ,
>
> Sorry but i didn't understand that If this is a bug from postgres version
> then how the same query will be worked if i recreated the tables and with
> same version of postgres.
>
>
This could be related to the plans that are chosen by the optimizer and
this specific error might be coming only when a certain plan is chosen.
When you recreated the table, the planner may have chosen a different plan
because the stats were different, and hence you did not see the issue
again. If you can reproduce the problem, it will be a good idea to run
EXPLAIN to see the query plan.
Thanks,
Pavan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2012-11-22 10:51:43 | Re: Fw: Postgresql on Windows 8 |
| Previous Message | Pavel Stehule | 2012-11-22 06:27:02 | Re: Prepared Statement Name Truncation |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavan Deolasee | 2012-11-22 06:55:32 | Re: [WIP PATCH] for Performance Improvement in Buffer Management |
| Previous Message | Karl O. Pinc | 2012-11-22 05:56:13 | Re: Doc patch: Document names of automatically created constraints and indexes |