Re: Disparity between 8.1.18 and 8.2.14 performance wise

From: "Dai, Tino" <tdai(at)loc(dot)gov>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Disparity between 8.1.18 and 8.2.14 performance wise
Date: 2010-03-23 15:22:13
Message-ID: 1CA7FF980DA3824F9A5C31532B7A40DCC4F6C43B@LCXCLMB01.LCDS.LOC.GOV
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

> 8.2 was released in 2006. 8.1 is going to be desupported entirely at
> the end of 2010. You really need to be holding your vendor's feet to
> the fire about supporting modern versions of Postgres, rather than
> looking for workarounds.

I think that is the correct move.

>> But having said that, I think 8.1 might generate a reasonable plan if it
>> weren't getting misled by these useless constraints:

>> -> Seq Scan on role_setting (cost=0.00..964.50 rows=1 width=70) (actual time=0.036..121.443 rows=43833 loops=1)
>> Filter: (((section)::text = (section)::text) AND (ref_id = ref_id))

> Can you get rid of those?

Unfortunately, I can't. The third-party product is protected by some kind of
obfuscation program. :( But is there any kind of external query rewrite tool
that can be put in front of postgres?

Thanks,
Tino

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2010-03-23 15:43:32 Re: pg_stat: last vacuum and analyze times are not being updated - v8.3.5
Previous Message Thorne, Francis 2010-03-23 15:14:10 Re: Supported Platforms for pgbouncer ?