Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id A42F72E35DD for ; Sun, 13 Jan 2008 16:12:28 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 77936-01 for ; Sun, 13 Jan 2008 16:12:24 -0400 (AST) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by postgresql.org (Postfix) with ESMTP id C4BD62E32B3 for ; Sun, 13 Jan 2008 16:12:24 -0400 (AST) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JE9Bo-00054z-NR for pgsql-admin@postgresql.org; Sun, 13 Jan 2008 20:12:16 +0000 Received: from 77.70.61.39 ([77.70.61.39]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 13 Jan 2008 20:12:16 +0000 Received: from milen by 77.70.61.39 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 13 Jan 2008 20:12:16 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: pgsql-admin@postgresql.org From: "Milen A. Radev" Subject: Re: large objects & space usage Date: Sun, 13 Jan 2008 22:12:10 +0200 Lines: 26 Message-ID: References: <200801131301.04468.kevin@kevinkempterllc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 77.70.61.39 User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) In-Reply-To: <200801131301.04468.kevin@kevinkempterllc.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.534 tagged_above=0 required=5 tests=AWL=-0.423, BAYES_05=-1.11, RCVD_NUMERIC_HELO=2.067 X-Spam-Level: X-Archive-Number: 200801/139 X-Sequence-Number: 27913 Kevin Kempter написа: > Hi List; > > I'm engaging with a client who is trying to solve what sounds like a bloat > issue. However in further conversations they told me this: > > 1) we have a table that is an integer key and a blob column > 2) the table was at 30Gig, we went in and deleted the last 2 months of data > and it's still at 30Gog > > At this point I thought bloat and that vacuum full or a table rebuild would > fix the issue. However later they told me: > > 3) we did a pg_dump and a reload into a database on the test box and the table > is still 30Gig. > > I haven't gotten access to their servers yet so I only have the above info > however I wonder is there special space considerations or storage > requirements, etc with blobs ? [...] So what is it - large objects or BYTEA? -- Milen A. Radev