From: | Brian Fehrle <brianf(at)consistentstate(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: View with and without ::text casting performs differently. |
Date: | 2013-09-18 18:50:05 |
Message-ID: | 5239F5DD.8090007@consistentstate.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 09/06/2013 12:35 PM, Tom Lane wrote:
> Brian Fehrle <brianf(at)consistentstate(dot)com> writes:
>> On 09/05/2013 05:50 PM, Tom Lane wrote:
>>> I rather doubt that the now-explicit-instead-of-implicit casts have much
>>> to do with that. It seems more likely that you forgot to re-ANALYZE in
>>> the new database, or there are some different planner settings, or
>>> something along that line.
>> I have two versions of the view in place on the same server, one with
>> the typecasting and one without, and this is where I see the differences
>> (no ::text runs in 0.5ms and with ::text runs in 13 or so minutes with
>> nested loop), so it's all running off the same statistics on the data.
> Hm. Can you provide a self-contained example?
I'll see what I can do to recreate this with bogus data. It's sensitive
data that may just be some sort of anomaly in terms of the data
distribution that is causing it.
- Brian F
>
> regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2013-09-18 20:28:53 | Re: [PERFORM] encouraging index-only scans |
Previous Message | Shaun Thomas | 2013-09-18 16:27:35 | Re: autovacuum and dead tuples |