Re: Select count(*), the sequel - Mailing list pgsql-performance

From Robert Haas
Subject Re: Select count(*), the sequel
Date
Msg-id AANLkTinLtyA3F8v-9nQKQW51LMOG+j7k_WEowPnQOPto@mail.gmail.com
Whole thread Raw
In response to Re: Select count(*), the sequel  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
On Tue, Oct 26, 2010 at 6:51 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.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

pgsql-performance by date:

Previous
From: Scott Marlowe
Date:
Subject: Re: CPUs for new databases
Next
From: Robert Haas
Date:
Subject: Re: HashJoin order, hash the large or small table? Postgres likes to hash the big one, why?