From: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
---|---|
To: | david(at)lang(dot)hm |
Cc: | "Steinar H(dot) Gunderson" <sgunderson(at)bigfoot(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Thousands of tables versus on table? |
Date: | 2007-06-06 07:29:35 |
Message-ID: | 4666625F.9010308@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
david(at)lang(dot)hm wrote:
> On Wed, 6 Jun 2007, Steinar H. Gunderson wrote:
>
>> On Tue, Jun 05, 2007 at 05:59:25PM -0400, Tom Lane wrote:
>>> I think the main argument for partitioning is when you are interested in
>>> being able to drop whole partitions cheaply.
>>
>> Wasn't there also talk about adding the ability to mark individual
>> partitions
>> as read-only, thus bypassing MVCC and allowing queries to be satisfied
>> using
>> indexes only?
>>
>> Not that I think I've seen it on the TODO... :-)
>
> now that's a very interesting idea, especially when combined with
> time-based data where the old times will never change.
That's been discussed, but it's controversial. IMHO a better way to
achieve that is to design the dead-space-map so that it can be used to
check which parts of a table are visible to everyone, and skip
visibility checks. That doesn't require any user action, and allows updates.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | weiping | 2007-06-06 07:40:57 | Re: different query plan because different limit # (Re: weird query plan) |
Previous Message | weiping | 2007-06-06 07:24:24 | different query plan because different limit # (Re: weird query plan) |