On 10/2/15 4:08 PM, Jonathan Vanasco wrote:
Using an even distribution as an example, the average width of the keys can
increase by 2 places:
Assuming you're using int4 or int8, then that doesn't matter. The only
other possible issue I can think of would be it somehow throwing the
planner st
Thanks for the reply.
On Oct 2, 2015, at 3:26 PM, Jim Nasby wrote:
> I'm not really following here... the size of an index is determined by the
> number of tuples in it and the average width of each tuple. So as long as
> you're using the same size of data type, 18 vs 1 sequence won't change t
On 10/1/15 6:48 PM, Jonathan Vanasco wrote:
1. general performance at different stages of DB size. with 18 sequences, our
keys/indexes are simply smaller than they'd be with 1 key. i wonder how this
will impact lookups and joins.
I'm not really following here... the size of an index is det
Hoping to glean some advice from the more experienced
The major component of our application currently tracks a few dozen object
types, and the total number of objects is in the 100s Millions range. Postgres
will potentially be tracking billions of objects.
Right now the primary key for ou
