pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Carey <scott@richrelevance.com>
To: Stephen Frost <sfrost@snowman.net>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Robert Schnabel <schnabelr@missouri.edu>
Cc: david@lang.hm <david@lang.hm>
Cc: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: How to best use 32 15k.7 300GB drives?
Date: Fri, 28 Jan 2011 09:50:47 -0800
Message-ID: <C9684183.1E40B%scott@richrelevance.com> (raw)
In-Reply-To: <20110128172810.GE30352@tamriel.snowman.net>



On 1/28/11 9:28 AM, "Stephen Frost" <sfrost@snowman.net> wrote:

>* Scott Marlowe (scott.marlowe@gmail.com) wrote:
>> There's nothing wrong with whole table updates as part of an import
>> process, you just have to know to "clean up" after you're done, and
>> regular vacuum can't fix this issue, only vacuum full or reindex or
>> cluster.
>
>Just to share my experiences- I've found that creating a new table and
>inserting into it is actually faster than doing full-table updates, if
>that's an option for you.

I wonder if postgres could automatically optimize that, if it thought that
it was going to update more than X% of a table, and HOT was not going to
help, then just create a new table file for XID's = or higher than the one
making the change, and leave the old one for old XIDs, then regular VACUUM
could toss out the old one if no more transactions could see it.


>
>    Thanks,
>
>        Stephen




view thread (24+ messages)  latest in thread

Message-ID: <C9684183.1E40B%scott@richrelevance.com>
Permalink:  ../C9684183.1E40B%25scott@richrelevance.com/
Also on:    postgresql.org/message-id/C9684183.1E40B%scott@richrelevance.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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: scott@richrelevance.com, sfrost@snowman.net, scott.marlowe@gmail.com, schnabelr@missouri.edu, david@lang.hm
  Subject: Re: How to best use 32 15k.7 300GB drives?
  In-Reply-To: <C9684183.1E40B%scott@richrelevance.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