I have no idea how good pg is with select queries over 365 partitions (1
year).
no need to use a partition per day, I'm pretty sure he won't mind having
a few extra days or weeks. I'd go by month, and drop a whole month at
a time, that way there's only 12-13 partitions.
and doing this,
From: [email protected]
[mailto:[email protected]] On Behalf Of Roger Tannous
Sent: Thursday, March 04, 2010 11:33 AM
To: [email protected]
Subject: [GENERAL] Optimal database table optimization method
Hello,
I have a database table that is growing
Heyho!
Disclaimer: I don't have much experience with big databases, so this is
based on my understanding of the theory.
On Thursday 04 March 2010 20.32:46 Roger Tannous wrote:
> I have a database table that is growing too big (few hundred million
> rows) that needs to be optimized, but before
Roger Tannous wrote:
Hello,
I have a database table that is growing too big (few hundred million
rows) that needs to be optimized, but before I get into partitioning
it, I thought I'd ask about suggestions.
Here is the usage:
0 . Table contains about 10 columns of length about 20 byte
Hello,
I have a database table that is growing too big (few hundred million rows)
that needs to be optimized, but before I get into partitioning it, I thought
I'd ask about suggestions.
Here is the usage:
0 . Table contains about 10 columns of length about 20 bytes each.
1.
INSERTS
