Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 17AF09FB558 for ; Fri, 9 Mar 2007 05:00:20 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 37873-10 for ; Fri, 9 Mar 2007 05:00:16 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from fmf.vtu.lt (fmf.vtu.lt [193.219.145.206]) by postgresql.org (Postfix) with ESMTP id 6CD189FB544 for ; Fri, 9 Mar 2007 05:00:16 -0400 (AST) Received: from fmf.vtu.lt (localhost [127.0.0.1]) by fmf.vtu.lt (Postfix) with ESMTP id 82DD71802A; Fri, 9 Mar 2007 11:00:11 +0200 (EET) Received: from 85.206.198.223 (SquirrelMail authenticated user nso) by fmf.vtu.lt with HTTP; Fri, 9 Mar 2007 11:00:11 +0200 (EET) Message-ID: <57425.85.206.198.223.1173430811.squirrel@fmf.vtu.lt> In-Reply-To: <200703091005.24820.achill@matrix.gatewaynet.com> References: <53561.85.206.198.223.1173384127.squirrel@fmf.vtu.lt> <200703091005.24820.achill@matrix.gatewaynet.com> Date: Fri, 9 Mar 2007 11:00:11 +0200 (EET) Subject: Re: Pg_dump and bytaA From: "Lukas" To: "Achilleas Mantzios" Cc: pgsql-admin@postgresql.org User-Agent: SquirrelMail/1.4.8 MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-VGTU-MailScanner-OpenProtect-Information: Please contact the ISP for more information X-VGTU-MailScanner-OpenProtect: Found to be clean X-MailScanner-OpenProtect-MCPCheck: X-MailScanner-OpenProtect-From: lukas@fmf.vtu.lt X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.455 tagged_above=0 required=5 tests=AWL, BAYES_50 X-Spam-Level: X-Archive-Number: 200703/32 X-Sequence-Number: 24856 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.. Lukas > Στις Πέμπτη 08 Μάρτιος 2007 22:02, ο/η Lukas > έγραψε: >> 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. > > -- This message has been scanned for viruses and dangerous content, and is believed to be clean.