On 12/14/05, Simon Riggs <[EMAIL PROTECTED]> wrote:
Maybe not for queries, but if you use a date range then you never needto run a DELETE and never need to VACUUM.You could split the data into two-day chunks.
That's an interesting idea, thanks.
> Am I using a horrid method for partitioning the data
On 12/12/05, Tom Lane <[EMAIL PROTECTED]> wrote:
Mike C <[EMAIL PROTECTED]> writes:> CLUSTER on PC_TRAFFIC_IDX3 gives me significantly improved performance:How can you tell? Neither of these are EXPLAIN ANALYZE output.
regards,
tom lane
Sorry that'
ster though and did pick up the correct child table. It was also a
bitmap scan on the index IIRC.Would I be better off creating many partial indexes instead of multiple tables AND multiple indexes?Am I using a horrid method for partitioning the data? (% 10)
Should there be that big of an improvement for multiple tables given that all the data is still stored on the same filesystem?
Any advice on table splitting much appreciated. Cheers,Mike C.
tr__( self ):
return "%s::int8"%(self.value,)
Enjoy,
Mike
___
Mike C. Fletcher
Designer, VR Plumber, Coder
http://members.rogers.com/mcfletch/
---(end of broadcast)---
TIP 7: don't forget to
s to take care
of PostgreSQL oddities.
Any other suggestions?
___
Mike C. Fletcher
Designer, VR Plumber, Coder
http://members.rogers.com/mcfletch/
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
