Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 5AC932E3746 for ; Fri, 18 Jan 2008 02:12:25 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 50129-06 for ; Fri, 18 Jan 2008 02:12:20 -0400 (AST) Received: from cubert.e-centre.net (morbo.e-centre.net [66.154.82.3]) by postgresql.org (Postfix) with ESMTP id 9C9AF2E36FD for ; Fri, 18 Jan 2008 02:12:22 -0400 (AST) Received: from [10.3.1.19] (helo=barracuda2.stayonline.net) by cubert.e-centre.net with esmtp (Exim 4.50) id 1JFkSE-0008LS-I2 for pgsql-admin@postgresql.org; Fri, 18 Jan 2008 01:11:54 -0500 X-ASG-Debug-ID: 1200631634-2619-77-0 X-Barracuda-URL: http://10.3.1.19:8000/cgi-bin/mark.cgi Received: from [172.16.1.87] (unknown [12.152.172.162]) by barracuda2.stayonline.net (Spam Firewall) with ESMTP id 913B71B2796B for ; Thu, 17 Jan 2008 23:47:14 -0500 (EST) From: Kevin Kempter To: pgsql-admin@postgresql.org X-ASG-Orig-Subj: more blob questions Subject: more blob questions Date: Thu, 17 Jan 2008 21:45:25 -0700 User-Agent: KMail/1.9.6 (enterprise 0.20071123.740460) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200801172145.25911.kevin@kevinkempterllc.com> X-Virus-Scanned: by Barracuda Spam Firewall at stayonline.net X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=4.0 tests= X-Barracuda-Spam-Report: Code version 3.02, rules version 3.0.65042 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.131 tagged_above=0 required=5 tests=BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13 X-Spam-Level: * X-Archive-Number: 200801/207 X-Sequence-Number: 27981 Hi List; Suppose I have a table with say an integer key, a char column and a large object column. can I simply delete a row from the table (delete from bigtable where...), then run a vacuum (or vacuum full) ? If so, in this scenario will postgres release the space back to the OS or must I first remove the large object with lo_unlink() ? also, does the contrib vacuumlo perform tasks I cannot do via vacuum and lo_unlink ? Thanks in advance.. /Kevin