Re: Select count(*), the sequel

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Kenneth Marshall <ktm(at)rice(dot)edu>, Mladen Gogala <mladen(dot)gogala(at)vmsinfo(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Select count(*), the sequel
Date: 2010-10-27 01:48:43
Message-ID: AANLkTinLtyA3F8v-9nQKQW51LMOG+j7k_WEowPnQOPto@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Tue, Oct 26, 2010 at 6:51 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> I don't think this is due to fillfactor - the default fillfactor is
>> 100, and anyway we ARE larger on disk than Oracle.  We really need to
>> do something about that, in the changes to NUMERIC in 9.1 are a step
>> in that direction, but I think a lot more work is needed.
>
> Of course, the chances of doing anything more than extremely-marginal
> kluges without breaking on-disk compatibility are pretty tiny.  Given
> where we are at the moment, I see no appetite for forced dump-and-reloads
> for several years to come.  So I don't foresee that anything is likely
> to come of such efforts in the near future.  Even if somebody had a
> great idea that would make things smaller without any other penalty,
> which I'm not sure I believe either.

Let's try not to prejudge the outcome without doing the research.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Robert Haas 2010-10-27 02:56:07 Re: HashJoin order, hash the large or small table? Postgres likes to hash the big one, why?
Previous Message Scott Marlowe 2010-10-27 01:14:26 Re: CPUs for new databases