Bruce,
Just to chime in. I also agree that fillfactor is useful. I have
been investigating different index variants and different fill
factors can greatly influence the performance of the index. I
also think it may play a key role in minimizing the small table/
many inserts/updates performance pro
1:50 PM
To: Rod Taylor
Cc: Darren King; Bruce Momjian; PostgreSQL Development
Subject: Re: [HACKERS] Minor TODO list changes
On Thu, 2004-11-04 at 18:15, Rod Taylor wrote:
> > At some point it would also be nice to be able to mark tables as
> > read-only and then any indexes created on
On Thu, 2004-11-04 at 18:15, Rod Taylor wrote:
> > At some point it would also be nice to be able to mark tables as
> > read-only and then any indexes created on that table after that would
> > have a fillfactor of 100%. Then I'd be able to load the table, alter it
> > to be read-only, then add th
On Thu, 2004-11-04 at 17:59, Darren King wrote:
> In my data warehousing situation, I'd like to be able to specify that
> the indexes be as compact as possible (fillfactor = 100%) in order to
> hit as few index pages as necessary.
>
Yes, that's my intent.
> At some point it would also be nice to
> At some point it would also be nice to be able to mark tables as
> read-only and then any indexes created on that table after that would
> have a fillfactor of 100%. Then I'd be able to load the table, alter it
> to be read-only, then add the appropriate indexes that are automatically
> compacte
-only, then add the appropriate indexes that are automatically
compacted.
Darren
-Original Message-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 04, 2004 12:19 PM
To: Simon Riggs
Cc: [EMAIL PROTECTED]
Subject: Re: [HACKERS] Minor TODO list changes
Simon Riggs
Simon Riggs wrote:
> On Thu, 2004-11-04 at 16:51, Bruce Momjian wrote:
> > OK, I updated all your items.
>
> Thanks
>
> > I removed fillfactor because I thought I
> > was the only one who thought it was valuable and as I remember it was
> > mostly useful for ISAM, which we don't support. Can y
On Thu, 2004-11-04 at 16:51, Bruce Momjian wrote:
> OK, I updated all your items.
Thanks
> I removed fillfactor because I thought I
> was the only one who thought it was valuable and as I remember it was
> mostly useful for ISAM, which we don't support. Can you think of a use
> for a non-100%
Added:
* Add fillfactor to control reserved free space during index
creation
---
Kenneth Marshall wrote:
> Bruce,
>
> Just to chime in. I also agree that fillfactor is useful. I have
> been investigating
Simon Riggs wrote:
>
> 4. Multiple column index statistics
>
> Allow accurate statistics to be collected on indexes that have more than
> one column, so that they are more frequently selected for use.
>
> (following on from Manfred Koizar's exploratory patch to provide
> this...)
Added.
--
OK, I updated all your items. I removed fillfactor because I thought I
was the only one who thought it was valuable and as I remember it was
mostly useful for ISAM, which we don't support. Can you think of a use
for a non-100% fillfactor?
On Thu, 4 Nov 2004, Simon Riggs wrote:
> REF INTEGRITY
>
> ...Didn't we just get rid of deferred triggers?? Perhaps I read that
> wrong.
We got rid of deferred referential actions. Constraint check triggers
for referential integrity (insert/update to fk table, NO ACTION on pk
table) are still d
On Thu, 2004-11-04 at 09:31, Simon Riggs wrote:
> A few minor typos/notes:
>
> INDEXES
>
> 1. On 2nd bullet...
> "The main difficulty with this item is the problem of creating an index
> that can spam more than one table."
>
> should be span, not spam
>
> 2. On 6th bullet
> * "Use index to re
A few minor typos/notes:
INDEXES
1. On 2nd bullet...
"The main difficulty with this item is the problem of creating an index
that can spam more than one table."
should be span, not spam
2. On 6th bullet
* "Use index to restrict rows returned by multi-key index when used
with non-consecuti
14 matches
Mail list logo
