Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WSLWM-00025k-Fr for pgsql-performance@arkaria.postgresql.org; Tue, 25 Mar 2014 07:11:38 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WSLWL-0000Rv-SL for pgsql-performance@arkaria.postgresql.org; Tue, 25 Mar 2014 07:11:37 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WSLWK-0000Ro-Lg for pgsql-performance@postgresql.org; Tue, 25 Mar 2014 07:11:36 +0000 Received: from mail-ob0-f175.google.com ([209.85.214.175]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WSLWH-0008Q2-Hp for pgsql-performance@postgresql.org; Tue, 25 Mar 2014 07:11:35 +0000 Received: by mail-ob0-f175.google.com with SMTP id uy5so65858obc.20 for ; Tue, 25 Mar 2014 00:11:33 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=9cFPTadU2Zaet5zVB5DRUnyostwkxfvjvtrxKIZELlQ=; b=FsAPioRpA1JvsN8ZnqppGpA3FATMOyWQWs5eZCSkMTZdJW0WTIaaQw1cld+WtoYJHx vPDqVfzOGx1eR9+5IN4yLUep2oY9VJRx7WKMpUBV1NbpyzUsrLUHXa2x3ULuQz1rPZVT usolMoxNtXxbwShPJHZGWLeZ1Vqm6bv6nSCOdN4OhprF1QS8aaVIy7c9tDiUkvcg7Y5u fP1BAagh9Xr6xTEK8ADLgIA4WbiI0z9HcW6g0+dRn2wIOqHCHE4K828j+zv1D00tbrhR bmxdhEREXP/HQno+kzmNfkdNllcuY5IG+eoUxwLKvFYvK3RaB1ZboTT2PtrIPPDL2k/O dW2w== X-Gm-Message-State: ALoCoQnDpbIfRxTBp02Y3q9NvYlHqjSXJHcBKfsaYIAZPHrZPctBSNqbCMVCJKVxb8VFbf54TBXJ MIME-Version: 1.0 X-Received: by 10.182.153.41 with SMTP id vd9mr10948obb.87.1395731492974; Tue, 25 Mar 2014 00:11:32 -0700 (PDT) Received: by 10.76.84.5 with HTTP; Tue, 25 Mar 2014 00:11:32 -0700 (PDT) X-Originating-IP: [95.90.121.141] Reply-To: ik@postgresql-consulting.com In-Reply-To: <1395722709.28433.YahooMailNeo@web161601.mail.bf1.yahoo.com> References: <1395722709.28433.YahooMailNeo@web161601.mail.bf1.yahoo.com> Date: Tue, 25 Mar 2014 08:11:32 +0100 Message-ID: Subject: Re: pg_dump vs pg_basebackup From: Ilya Kosmodemiansky To: gianfranco caca Cc: "pgsql-performance@postgresql.org" Content-Type: text/plain; charset=ISO-8859-1 X-Pg-Spam-Score: -2.6 (--) 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 Hi gianfranco, How exactly large is your database and how heavy is a workload on it? Usually if you have more than ~200Gb, better to use pg_basebackup because pg_dump will take too long time. And please take in mind, that pg_dump makes dump, which is actually not the same thing as a backup. Best regards, Ilya On Tue, Mar 25, 2014 at 5:45 AM, gianfranco caca wrote: > Hai, > > Can anyone tell me the difference and performance between pgdump and > pg_basebackup if I want to backup a large database. > > Thanks -- Ilya Kosmodemiansky, PostgreSQL-Consulting.com tel. +14084142500 cell. +4915144336040 ik@postgresql-consulting.com -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance