Re: [GENERAL] array column and b-tree index allowing only 8191 bytes

2008-06-12 Thread Alvaro Herrera
Celso Pinto wrote: > What, if any, would be the recommended options to improve this > scenario? Not using intarray? :-) Not using a broken design. Arrays are a poor fit in the relational model. Avoid them. -- Alvaro Herrerahttp://www.CommandPrompt.com/ PostgreS

Re: [GENERAL] array column and b-tree index allowing only 8191 bytes

2008-06-11 Thread Celso Pinto
Hi Alvaro, thanks for the hint. I've since experimented with gin and gist and did a small pgbench custom script test. Recalling from my previous message, the int[] on a row can have a maximum of 5000 values. From here I judged gin to be the best option but inserting is really slow. The test was p

Re: [GENERAL] array column and b-tree index allowing only 8191 bytes

2008-06-07 Thread Alvaro Herrera
Celso Pinto wrote: > So my questions are: is this at all possible? If so, is is possible to > increate that maximum size? Indexing the arrays themselves is probably pretty useless. Try indexing the elements, which you can do with the intarray contrib module. -- Alvaro Herrera

[GENERAL] array column and b-tree index allowing only 8191 bytes

2008-06-06 Thread Celso Pinto
Hi all, I'm checking out some features in pgsql and found out about an array datatype. As I'm curious to find out how well it performs, I've created a table that contains an integer[] column and a script to insert about 500K rows in it. The length for the integer[] column is random (can be 10, can