From: | Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #6662: Database do not push condition to subquery, test case for bug 6658 |
Date: | 2012-05-23 02:18:47 |
Message-ID: | CAK-MWwSQNbK8=Ufgnu8k0cToCcYgu3HamJRo3Ujgn89uJyg6bA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, May 23, 2012 at 12:14 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com> writes:
> > if anytextcat() and textanycat() are marked volatile,
> > why the database allows create index on supposedly to be volatile
> > expression:
> > create index test_val_special on test((val || ''));
>
> CREATE INDEX inlines anytextcat (which is just a SQL function) before
> making the volatility test, cf commit 5a86e5e19. The reason the
> subselect flattening code has difficulty with this case is that that
> happens before function inlining does, so the expression still looks
> volatile even though it really isn't.
>
> regards, tom lane
>
Thank you very much for all detailed explanation and all help.
Kind Regards,
Maksym
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2012-05-23 03:24:40 | Re: BUG #6626: union all with values of type "unknown" |
Previous Message | Tom Lane | 2012-05-23 02:14:48 | Re: BUG #6662: Database do not push condition to subquery, test case for bug 6658 |