Re: Does writing new records while massive update will generate lock ? - Mailing list pgsql-general

From Alban Hertroys
Subject Re: Does writing new records while massive update will generate lock ?
Date
Msg-id CAF-3MvOGPxYbe71o+Esn-TVuSwnHjvoaGUO=ySrqwx2en1-FTg@mail.gmail.com
Whole thread Raw
In response to Does writing new records while massive update will generate lock ?  (Victor d'Agostino <victor.d.agostino@fiducial.net>)
List pgsql-general

On 21 August 2014 15:41, Victor d'Agostino <victor.d.agostino@fiducial.net> wrote:
I'm updating this column (for more than 48 hours now) on a RAID5 server.

RAID5? That's probably the worst performing RAID configuration you can have and is usually advised against on this list.
You would be better off with RAID 10, RAID 1+0 or even RAID 1, but you would be using more disk space.

That said, if your IO is not being saturated by that query, you could split the update across multiple CPU's by dividing up the email_id's over multiple queries that you run from a session each.

--
If you can't see the forest for the trees,
Cut the trees and you'll see there is no forest.

pgsql-general by date:

Previous
From: Raymond O'Donnell
Date:
Subject: Re: Does writing new records while massive update will generate lock ?
Next
From: Steve Kehlet
Date:
Subject: hot_standby_feedback vs. max_standby_archive_delay/max_standby_streaming_delay?