From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | sthomas(at)peak6(dot)com |
Cc: | Marti Raudsepp <marti(at)juffo(dot)org>, Magnus Hagander <magnus(at)hagander(dot)net>, Svetlin Manavski <svetlin(dot)manavski(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: seq scan in the case of max() on the primary key column |
Date: | 2011-06-22 18:12:37 |
Message-ID: | BANLkTi=g0OfJkf_tA89V+P=J=X2WWKdHPw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Wed, Jun 22, 2011 at 7:12 AM, Shaun Thomas <sthomas(at)peak6(dot)com> wrote:
> On 06/22/2011 04:55 AM, Marti Raudsepp wrote:
>
>> With Jim Nasby's idea to use regclass instead of relation names, the
>> function is now half its length and probably more reliable. There's no
>> need to touch pg_class directly at all.
>
> Sadly until we upgrade to EDB 9.0, I have to use my function. :) EDB 8.3
> (which is really PostgreSQL 8.2) doesn't have a regclass->text conversion.
> But I'll bookmark the wiki page anyway, so I can update my function after
> upgrading. Heh.
>
Given that many folks still run < 9.0 in production, the wiki page
should really have a version of that function for older versions,
whether it's long or not.
From | Date | Subject | |
---|---|---|---|
Next Message | Shaun Thomas | 2011-06-22 18:15:13 | Re: seq scan in the case of max() on the primary key column |
Previous Message | Greg Smith | 2011-06-22 17:01:43 | Re: seq scan in the case of max() on the primary key column |