Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 581E59FBAF6 for ; Fri, 9 Mar 2007 10:27:16 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 98090-03-6 for ; Fri, 9 Mar 2007 10:27:09 -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 1104E9FBB0D for ; Fri, 9 Mar 2007 10:27:09 -0400 (AST) Received: from fmf.vtu.lt (localhost [127.0.0.1]) by fmf.vtu.lt (Postfix) with ESMTP id DC91D1802A; Fri, 9 Mar 2007 16:27:03 +0200 (EET) Received: from 213.164.99.172 (SquirrelMail authenticated user nso) by fmf.vtu.lt with HTTP; Fri, 9 Mar 2007 16:27:03 +0200 (EET) Message-ID: <65191.213.164.99.172.1173450423.squirrel@fmf.vtu.lt> In-Reply-To: References: <53561.85.206.198.223.1173384127.squirrel@fmf.vtu.lt> <200703091150.09431.achill@matrix.gatewaynet.com> <200703091518.04492.achill@matrix.gatewaynet.com> Date: Fri, 9 Mar 2007 16:27:03 +0200 (EET) Subject: Re: Pg_dump and bytaA From: "Lukas" To: "Milen A. Radev" 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.304 tagged_above=0 required=5 tests=AWL, BAYES_50 X-Spam-Level: X-Archive-Number: 200703/37 X-Sequence-Number: 24861 -b --blobs Include large objects in dump. Examples To dump a database: $ pg_dump mydb > db.out To dump a database called mydb that contains large objects to a tar file: $ pg_dump -Ft -b mydb > db.tar > Achilleas Mantzios wrote: >> Στις Παρασκευή 09 Μάρτιος 2007 15:05, ο/η Milen A. >> Radev έγραψε: >>> Achilleas Mantzios wrote: >>>> Στις Παρασκευή 09 Μάρτιος 2007 11:00, ο/η Lukas >>>> έγραψε: >>>>> 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 >>>> 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. >>> How to exclude them from a custom dump? (That's for version 8.1/8.2) >> >> you just dont include them :) > > Yes, and how exactly you do not include them? > > For example - this is my backup script that is executed nightly: > > ------------------------------------------------------------------- > PSQL=/usr/local/pgsql/bin/psql > PG_DUMP=/usr/local/pgsql/bin/pg_dump > PG_DUMPALL=/usr/local/pgsql/bin/pg_dumpall > > > $PG_DUMPALL -U postgres --globals-only > $BACKUPDIR/pg_globals.sql > > for db in `$PSQL -U postgres -d template1 -t -c "SELECT datname FROM > pg_catalog.pg_database WHERE datname "\!"~ 'template(0|1)';"` > do > echo -n -e "Dumping database $db...\t\t" > $PG_DUMP -U postgres --format=c $db > $BACKUPDIR/$db.dump > echo "done." > done > ------------------------------------------------------------------- > > Guess what? There was a special command-line parameter for including > large objects in the custom/tar dump until version 8.1 > (http://www.postgresql.org/docs/8.0/static/app-pgdump.html, look for > "--blobs"). Now they are included by default AND could not be excluded, > at least I could not find a way to do that > (http://www.postgresql.org/docs/8.1/static/app-pgdump.html). > > So what are you suggesting? > > > -- > Milen A. Radev > > > ---------------------------(end of broadcast)--------------------------- > TIP 1: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly > > -- > 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.