X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 6E76311F6081 for ; Tue, 25 Apr 2006 18:11:00 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 33410-09 for ; Tue, 25 Apr 2006 18:10:49 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from morpheus.bostonstock.com (unknown [192.233.205.44]) by postgresql.org (Postfix) with ESMTP id 53B2911F6083 for ; Tue, 25 Apr 2006 18:10:47 -0300 (ADT) Received: by MORPHEUS with Internet Mail Service (5.5.2653.19) id <2R02AWJ2>; Tue, 25 Apr 2006 17:06:25 -0400 Message-ID: <0C4841B42F87D51195BD00B0D020F5CB044B2586@MORPHEUS> From: "mcelroy, tim" To: "'pgsql-admin@postgresql.org'" Subject: Re: dbsize & pg_dump Date: Tue, 25 Apr 2006 17:06:24 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C668AC.04E3DDC6" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200604/271 X-Sequence-Number: 21440 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C668AC.04E3DDC6 Content-Type: text/plain; charset="iso-8859-1" Please disregard this question. I'm using pg_dump -F c which compresses the data a it backs it up. Tim -----Original Message----- From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org]On Behalf Of mcelroy, tim Sent: Tuesday, April 25, 2006 4:40 PM To: 'pgsql-admin@postgresql.org' Subject: [ADMIN] dbsize & pg_dump Good afternoon, Probably an easy question but why are the file sizes differ so much between these two tools? For example: A backup using pg_dump of our largest DB creates a file 384MB in size Using the following SQL code utilizing dbsize I get the following: FIX1=# SELECT D1.pg_size_pretty AS "FIX1_DB_SIZE" FIX1-# FROM (SELECT pg_size_pretty(database_size('FIX1'))) D1; FIX1_DB_SIZE -------------- 3832 MB (1 row) Is it safe to assume that pg_dump does a compression of the data? Thanks Tim ------_=_NextPart_001_01C668AC.04E3DDC6 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable dbsize & pg_dump

P= lease disregard this question.  = I’m using pg_dump –F c which compresses the data a it backs it = up.

<= ![if = !supportEmptyParas]> 

=

T= im

<= ![if = !supportEmptyParas]> 

=

<= ![if = !supportEmptyParas]> 

=

-----Original Message-----
From: pgsql-admin-owner@postgresql.org = [mailto:pgsql-admin-owner@postgresql.org]On Behalf Of mcelroy, tim
Sent: Tuesday, April 25, = 2006 4:40 PM
To: = 'pgsql-admin@postgresql.org'
Subject: [ADMIN] dbsize = & pg_dump

 

Good = afternoon,=

Probably an = easy question but why are the file sizes differ so much between = these two tools?

For = example:  =

A backup using = pg_dump of our largest DB creates a file 384MB in = size=

Using the = following SQL code utilizing dbsize I get the following:=

FIX1=3D# SELECT D1.pg_size_pretty AS "FIX1_DB_SIZE"=

FIX1-# FROM = (SELECT pg_size_pretty(database_size('FIX1'))) D1;=

 FIX1_DB_SI= ZE=

--------------=

 3832 = MB=

(1 row)=

Is it safe to = assume that pg_dump does a compression of the data?=

Thanks=

Tim=

------_=_NextPart_001_01C668AC.04E3DDC6--