Re: Rearchitecting for storage

From: Kenneth Marshall <ktm(at)rice(dot)edu>
To: Matthew Pounsett <matt(at)conundrum(dot)com>
Cc: Luca Ferrari <fluca1978(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Rearchitecting for storage
Date: 2019-07-19 14:56:33
Message-ID: 20190719145633.GB28959@aart.rice.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi Matt,

On Fri, Jul 19, 2019 at 10:41:31AM -0400, Matthew Pounsett wrote:
> On Fri, 19 Jul 2019 at 04:21, Luca Ferrari <fluca1978(at)gmail(dot)com> wrote:
>
> >
> > This could be trivial, but any chance you can partition the table
> > and/or archive unused records (at least temporarly)? A 18 TB table
> > quite frankly sounds a good candidate to contain records no one is
> > interested in the near future.
> >
>
> Partitioning is a possibility. The whole database is historical test
> results, stored specifically for doing comparisons over time, so I'm not
> sure we can actually archive anything. Expiring old test data is a
> discussion we might have to have, eventually.
>

This is a case were using a compressed filesystem can give you space
savings as well as faster read performance due to the compression
factor. In my case a sequential scan of something in the compressed
tablespace runs almost 3X faster than on the non-compressed one.

Regards,
Ken

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Matthew Pounsett 2019-07-19 15:06:23 Re: Rearchitecting for storage
Previous Message Matthew Pounsett 2019-07-19 14:41:31 Re: Rearchitecting for storage