Re: [pgsql-advocacy] [PERFORM] Postgres and really huge tables

2007-01-19 Thread Oleg Bartunov
On Thu, 18 Jan 2007, Tom Lane wrote: Brian Hurt [EMAIL PROTECTED] writes: Is there any experience with Postgresql and really huge tables? I'm talking about terabytes (plural) here in a single table. The 2MASS sky survey point-source catalog

Re: [PERFORM] Postgres and really huge tables

2007-01-19 Thread Merlin Moncure
On 1/18/07, Brian Hurt [EMAIL PROTECTED] wrote: Is there any experience with Postgresql and really huge tables? I'm talking about terabytes (plural) here in a single table. Obviously the table will be partitioned, and probably spread among several different file systems. Any other tricks I

[PERFORM] Postgres and really huge tables

2007-01-18 Thread Brian Hurt
Is there any experience with Postgresql and really huge tables? I'm talking about terabytes (plural) here in a single table. Obviously the table will be partitioned, and probably spread among several different file systems. Any other tricks I should know about? We have a problem of that

Re: [PERFORM] Postgres and really huge tables

2007-01-18 Thread Scott Marlowe
On Thu, 2007-01-18 at 14:31, Brian Hurt wrote: Is there any experience with Postgresql and really huge tables? I'm talking about terabytes (plural) here in a single table. Obviously the table will be partitioned, and probably spread among several different file systems. Any other tricks

Re: [PERFORM] Postgres and really huge tables

2007-01-18 Thread Tom Lane
Brian Hurt [EMAIL PROTECTED] writes: Is there any experience with Postgresql and really huge tables? I'm talking about terabytes (plural) here in a single table. The 2MASS sky survey point-source catalog http://www.ipac.caltech.edu/2mass/releases/allsky/doc/sec2_2a.html is 470 million rows by

Re: [PERFORM] Postgres and really huge tables

2007-01-18 Thread Gavin Sherry
Hi Brian, On Thu, 18 Jan 2007, Brian Hurt wrote: Is there any experience with Postgresql and really huge tables? I'm talking about terabytes (plural) here in a single table. Obviously the table will be partitioned, and probably spread among several different file systems. Any other tricks