From: | Rod Taylor <rod(dot)taylor(at)gmail(dot)com> |
---|---|
To: | Sebastián Baioni <sebastianbaioni(at)yahoo(dot)com(dot)ar> |
Cc: | Performance PostgreSQL <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Backup/Restore too slow |
Date: | 2006-12-29 17:28:49 |
Message-ID: | 6D5957CD-46A9-42E5-B644-12FB078F479A@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Rebuilding the indexes or integrity confirmations are probably taking
most of the time.
What is your work_mem setting?
On 22-Dec-06, at 9:32 AM, Sebastián Baioni wrote:
> Hi,
> We have a database with one table of 10,000,000 tuples and 4 tables
> with 5,000,000 tuples.
> While in SQL Server it takes 3 minutes to restore this complete
> database, in PostgreSQL it takes more than 2 hours.
> The Backup takes 6 minutes in SQLServer and 13 minutes (which is
> not a problem)
>
> We are running PostgreSQL 8.1 for Windows and we are using:
> C:\pg_dump.exe -i -h localhost -p 5432 -U usuario -F c -b -v -f "C:
> \BK\file.backup" base
> and
> C:\pg_restore.exe -i -h localhost -p 5432 -U usuario -d base -O -v
> "C:\BK\file.backup"
>
> We use those parameters because we copied them from PGAdminIII.
>
> Is there any way to make it faster?
>
> Tanks
> Sebastián
> __________________________________________________
> Correo Yahoo!
> Espacio para todos tus mensajes, antivirus y antispam ¡gratis!
> ¡Abrí tu cuenta ya! - http://correo.yahoo.com.ar
From | Date | Subject | |
---|---|---|---|
Next Message | Rod Taylor | 2006-12-29 17:32:39 | Re: What you would consider as heavy traffic? |
Previous Message | Arnau | 2006-12-29 14:26:15 | Re: High update activity, PostgreSQL vs BigDBMS |