pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Ribe <scott_ribe@elevated-dev.com>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Kido Kouassi <jjkido@gmail.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Read performance on Large Table
Date: Thu, 21 May 2015 09:18:30 -0600
Message-ID: <580E17C5-363E-4D24-B381-80A1F4C83C81@elevated-dev.com> (raw)
In-Reply-To: <CAOR=d=3Ft9x+r0N30a_ASgLtSDFNA_m-H7_-sdFuOqD3FRyjPg@mail.gmail.com>
References: <CA+ebzukaZJVOjw2Vqg0cuCUqbaEEHHuCa-pNbsX6CWAZyga3Fw@mail.gmail.com>
	<CAOR=d=3Ft9x+r0N30a_ASgLtSDFNA_m-H7_-sdFuOqD3FRyjPg@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

On May 21, 2015, at 9:05 AM, Scott Marlowe <scott.marlowe@gmail.com> wrote:
> 
> I've done a lot of partitioning of big data sets in postgresql and if
> there's some common field, like data, that makes sense to partition
> on, it can be a huge win.

Indeed. I recently did it on exactly this kind of thing, a log of activity. And the common queries weren’t slow at all.

But if I wanted to upgrade via dump/restore with minimal downtime, rather than set up Slony or try my luck with pg_upgrade, I could dump the historical partitions, drop those tables, then dump/restore, then restore the historical partitions at my convenience. (In this particular db, history is unusually huge compared to the live data.)

-- 
Scott Ribe
scott_ribe@elevated-dev.com
http://www.elevated-dev.com/
https://www.linkedin.com/in/scottribe/
(303) 722-0567 voice







-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



view thread (12+ messages)  latest in thread

Message-ID: <580E17C5-363E-4D24-B381-80A1F4C83C81@elevated-dev.com>
Permalink:  ../580E17C5-363E-4D24-B381-80A1F4C83C81@elevated-dev.com/
Also on:    postgresql.org/message-id/580E17C5-363E-4D24-B381-80A1F4C83C81@elevated-dev.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: scott_ribe@elevated-dev.com, scott.marlowe@gmail.com, jjkido@gmail.com
  Subject: Re: Read performance on Large Table
  In-Reply-To: <580E17C5-363E-4D24-B381-80A1F4C83C81@elevated-dev.com>
  References: <CA+ebzukaZJVOjw2Vqg0cuCUqbaEEHHuCa-pNbsX6CWAZyga3Fw@mail.gmail.com> <CAOR=d=3Ft9x+r0N30a_ASgLtSDFNA_m-H7_-sdFuOqD3FRyjPg@mail.gmail.com> <580E17C5-363E-4D24-B381-80A1F4C83C81@elevated-dev.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox