Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UemcP-00063d-GF for pgsql-performance@arkaria.postgresql.org; Tue, 21 May 2013 13:28:45 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1UemcP-0001uO-0h for pgsql-performance@arkaria.postgresql.org; Tue, 21 May 2013 13:28:45 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UemcN-0001uI-Mx for pgsql-performance@postgresql.org; Tue, 21 May 2013 13:28:44 +0000 Received: from mail-la0-x231.google.com ([2a00:1450:4010:c03::231]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UemcG-0000Dr-H2 for pgsql-performance@postgresql.org; Tue, 21 May 2013 13:28:42 +0000 Received: by mail-la0-f49.google.com with SMTP id fp13so665558lab.8 for ; Tue, 21 May 2013 06:28:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=czzVX1awB8ewt1d9LPn/m60S2MLf5C2FzqTO8/MZYKI=; b=e1fjWRCjztt2uOWPkGhZnMh+J6a9XGbkUdHOFXMQVnnhwa3BPBnrr0qsKHqSFZj1mJ UZrmu6VKEA34o9+ErAOSX1L/DXXdCPGjRe3y9vkvkykVtshLNaH1mNObsjS7aEoHCgcI v262qMBnfQzOEi/yTXHnUCM2q/amOeErcx4tAy4KfHhzc1AKnLhSt5VgmeNKDz4EzFxH ohH9NIx0sdI8y4jkg5AikytrIOv117vB7ILRELbdQSldDKN6KXVl7xnDOJycyBiy0Se/ Py+zPVVaOg9OhlL98gMJxlOUNe12Jw5ouGeI4pqK/Cd+clU2GMaH6U/3sXCXGN/43diY 1zTg== X-Received: by 10.112.202.198 with SMTP id kk6mr1573197lbc.4.1369142914515; Tue, 21 May 2013 06:28:34 -0700 (PDT) Received: from [192.168.4.22] ([217.174.184.92]) by mx.google.com with ESMTPSA id w9sm1184654lbe.6.2013.05.21.06.28.32 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 May 2013 06:28:33 -0700 (PDT) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: performance database for backup/restore From: Evgeny Shishkin In-Reply-To: <519B743F.7040407@audifarma.com.co> Date: Tue, 21 May 2013 17:28:31 +0400 Cc: pgsql-performance@postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: <39946120-F3C6-4EEF-8686-E541F865ED5A@gmail.com> References: <519B743F.7040407@audifarma.com.co> To: Jeison Bedoya X-Mailer: Apple Mail (2.1503) X-Pg-Spam-Score: 0.7 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org On May 21, 2013, at 5:18 PM, Jeison Bedoya wrote: > Hi people, i have a database with 400GB running in a server with 128Gb RA= M, and 32 cores, and storage over SAN with fiberchannel, the problem is whe= n i go to do a backup whit pg_dumpall take a lot of 5 hours, next i do a re= store and take a lot of 17 hours, that is a normal time for that process in= that machine? or i can do something to optimize the process of backup/rest= ore. >=20 I'd recommend you to dump with=20 pg_dump --format=3Dc It will compress the output and later you can restore it in parallel with pg_restore -j 32 (for example) Right now you can not dump in parallel, wait for 9.3 release. Or may be som= eone will back port it to 9.2 pg_dump. Also during restore you can speed up a little more by disabling fsync and s= ynchronous_commit.=20 > This is my current configuration >=20 > Postgres version 9.2.2 > connections 1000 > shared buffers 4096MB > work_mem =3D 2048MB > maintenance_work_mem =3D 2048MB > checkpoint_segments =3D 103 >=20 > the other params are by default. >=20 > Thankyou very much >=20 > --=20 > Atentamente, >=20 >=20 > JEISON BEDOYA DELGADO > Adm. Servidores y Comunicaciones > AUDIFARMA S.A. >=20 >=20 > -- > NOTA VERDE: > No imprima este correo a menos que sea absolutamente necesario. > Ahorre papel, ayude a salvar un arbol. >=20 > -------------------------------------------------------------------- > Este mensaje ha sido analizado por MailScanner > en busca de virus y otros contenidos peligrosos, > y se considera que esta limpio. >=20 > -------------------------------------------------------------------- > Este texto fue anadido por el servidor de correo de Audifarma S.A.: >=20 > Las opiniones contenidas en este mensaje no necesariamente coinciden > con las institucionales de Audifarma. La informacion y todos sus > archivos Anexos, son confidenciales, privilegiados y solo pueden ser > utilizados por sus destinatarios. Si por error usted recibe este > mensaje, le ofrecemos disculpas, solicitamos eliminarlo de inmediato, > notificarle de su error a la persona que lo envio y abstenerse de > utilizar su contenido. >=20 >=20 >=20 >=20 > --=20 > Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-performance --=20 Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance