Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id D9D829FB434 for ; Fri, 9 Mar 2007 05:50:17 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024) with ESMTP id 30710-04 for ; Fri, 9 Mar 2007 05:50:08 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from matrix.gatewaynet.com (host2.dynacom.ondsl.gr [62.103.35.210]) by postgresql.org (Postfix) with ESMTP id 750FD9FB463 for ; Fri, 9 Mar 2007 05:50:11 -0400 (AST) Received: from host3.dynacom.ondsl.gr ([62.103.35.211] helo=ip216.internal.net) by matrix.gatewaynet.com with esmtp (Exim 4.62) (envelope-from ) id 1HPbjl-0007MH-QS; Fri, 09 Mar 2007 11:50:09 +0200 From: Achilleas Mantzios Organization: Dynacom Tankers Mgmt To: "Lukas" Subject: Re: Pg_dump and bytaA Date: Fri, 9 Mar 2007 11:50:08 +0200 User-Agent: KMail/1.9.3 Cc: pgsql-admin@postgresql.org References: <53561.85.206.198.223.1173384127.squirrel@fmf.vtu.lt> <200703091005.24820.achill@matrix.gatewaynet.com> <57425.85.206.198.223.1173430811.squirrel@fmf.vtu.lt> In-Reply-To: <57425.85.206.198.223.1173430811.squirrel@fmf.vtu.lt> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200703091150.09431.achill@matrix.gatewaynet.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.169 tagged_above=0 required=5 tests=AWL, BAYES_50, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200703/33 X-Sequence-Number: 24857 =CE=A3=CF=84=CE=B9=CF=82 =CE=A0=CE=B1=CF=81=CE=B1=CF=83=CE=BA=CE=B5=CF=85= =CE=AE 09 =CE=9C=CE=AC=CF=81=CF=84=CE=B9=CE=BF=CF=82 2007 11:00, =CE=BF/=CE= =B7 Lukas =CE=AD=CE=B3=CF=81=CE=B1=CF=88=CE=B5: > Hello, > > pg_dump can avoid bloob fields (it can dumb without blobs), but as I > understand byteA is not bloob, so in this case what is blob? I did not > found such type as blob.. > Take a look at=20 http://www.postgresql.org/docs/7.4/interactive/largeobjects.html You might also consider writing a program for transforming your db/app from bytea based to large object based, and simply exclude blobs from your pg_dump's. > Lukas > > > =CE=A3=CF=84=CE=B9=CF=82 =CE=A0=CE=AD=CE=BC=CF=80=CF=84=CE=B7 08 =CE=9C= =CE=AC=CF=81=CF=84=CE=B9=CE=BF=CF=82 2007 22:02, =CE=BF/=CE=B7 Lukas > > > > =CE=AD=CE=B3=CF=81=CE=B1=CF=88=CE=B5: > >> Hello, > >> > >> we have one table in database (db has over 200 tables), which has one > >> byteA filed for storing user photos. We are making backup every night, > >> but > >> it is now too large because of photos. We do not need to make backup of > >> photos every night, but the question is how to backup database without > >> this field? > >> I tried to look at keys of pgdump, but found nothing... > > > > This isnt directly possible. > > You could have a mirror of the database, > > and nullify these bytea columns in the mirror db before > > taking the dump of this mirror db. > > > >> Now we are using it like this: > >> pg_dump -f /home/backup/DB.sql -d -Fp -v DB > >> > >> thx > >> Lukas > > > > -- > > Achilleas Mantzios > > > > ---------------------------(end of broadcast)--------------------------- > > TIP 3: Have you checked our extensive FAQ? > > > > http://www.postgresql.org/docs/faq > > > > -- > > This message has been scanned for viruses and > > dangerous content, and is believed to be clean. =2D-=20 Achilleas Mantzios