pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Palle Girgensohn <girgen@pingpong.net>
To: Robert Treat <xzilla@users.sourceforge.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: reduce downtime when upgrading 7.3 -> 7.4
Date: Tue, 10 Feb 2004 17:24:08 +0100
Message-ID: <51450000.1076430248@rambutan.pingpong.net> (raw)
In-Reply-To: <1076423601.17917.8.camel@camel>
References: <331690000.1076207705@palle.girgensohn.se>
	<1076423601.17917.8.camel@camel>

--On Tuesday, February 10, 2004 09:33:20 -0500 Robert Treat 
<xzilla@users.sourceforge.net> wrote:

> On Sat, 2004-02-07 at 21:35, Palle Girgensohn wrote:
>> Hi,
>>
>> We use postgresql for rather large databases. For a typical
>> installation, a  pg_restore takes a couple of hours, at least (the
>> dumpfiles are usually 2-4  gigabytes or so, including BLOBs). The
>> machines are expected to be up 24/7,  so this dump/restore procedure
>> makes upgrading unpopular. Is there any  (safe) way to speed this
>> process up?
>>
>> If pg_upgrade is not a good idea, how can I speed up pg_restore? Best
>> way  to set things like fsync etc in postgresql.conf? Will it make a big
>> difference?
>>
>
> yes, setting fsync off should make a significant difference. I usually
> recommend it cause if there is a machine failure during restore I will
> want to start the process again anyway.  Other items you should probably
> change are cranking up sort_mem significantly (if your restore is the
> only process running, let it take up most of the ram on the box) and you
> can increase check_point segments as well.  HTH

Thanks, I'll try this.

Regards,
Palle




view thread (6+ messages)  latest in thread

Message-ID: <51450000.1076430248@rambutan.pingpong.net>
Permalink:  ../51450000.1076430248@rambutan.pingpong.net/
Also on:    postgresql.org/message-id/51450000.1076430248@rambutan.pingpong.net

 · 

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: girgen@pingpong.net, xzilla@users.sourceforge.net
  Subject: Re: reduce downtime when upgrading 7.3 -> 7.4
  In-Reply-To: <51450000.1076430248@rambutan.pingpong.net>
  References: <331690000.1076207705@palle.girgensohn.se> <1076423601.17917.8.camel@camel> <51450000.1076430248@rambutan.pingpong.net>

* 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