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

From: Jonathan Vanasco <postgres(at)2xlp(dot)com>
To: PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org>
Subject: Re: splitting up tables based on read/write frequency of columns
Date: 2015-01-21 15:36:52
Message-ID: D0D8DE09-9A28-4F43-B014-6F04350D2329@2xlp.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


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 come in handy for some analytic stuff we run!

I know that PG can handle my current system "at scale". I'm really just wondering what the possible slowdowns/improvements will be.

Doing a rewrite of the entire row + updating the various indexes seems to be a lot of unnecessary IO. At some point it will make sense to minimize that and isolate the heavy-write columns from impacting the rest of the table's performance.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Raymond O'Donnell 2015-01-21 15:37:31 Re: Fwd: Ask for a question
Previous Message Pierre Hsieh 2015-01-21 14:38:55 Fwd: Ask for a question