Re: [GENERAL] splitting up tables based on read/write frequency of columns

2015-01-21 Thread David G Johnston
Jonathan Vanasco-7 wrote > This is really a theoretical/anecdotal question, as I'm not at a scale yet > where this would measurable. I want to investigate while this is fresh in > my mind... > > I recall reading that unless a row has columns that are TOASTed, an > `UPDATE` is essentially an `INSE

Re: [GENERAL] splitting up tables based on read/write frequency of columns

2015-01-21 Thread Jonathan Vanasco
On Jan 19, 2015, at 5:07 PM, Stefan Keller wrote: > Hi > > I'm pretty sure PostgreSQL can handle this. > But since you asked with a theoretic background, > it's probably worthwhile to look at column stores (like [1]). Wow. I didn't know there was a column store extension for PG -- this would c

Re: [GENERAL] splitting up tables based on read/write frequency of columns

2015-01-19 Thread Stefan Keller
Hi I'm pretty sure PostgreSQL can handle this. But since you asked with a theoretic background, it's probably worthwhile to look at column stores (like [1]). -S. [*] http://citusdata.github.io/cstore_fdw/ 2015-01-19 22:47 GMT+01:00 Jonathan Vanasco : > This is really a theoretical/anecdotal que

[GENERAL] splitting up tables based on read/write frequency of columns

2015-01-19 Thread Jonathan Vanasco
This is really a theoretical/anecdotal question, as I'm not at a scale yet where this would measurable. I want to investigate while this is fresh in my mind... I recall reading that unless a row has columns that are TOASTed, an `UPDATE` is essentially an `INSERT + DELETE`, with the previous ro