Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id CAA60233; Tue, 25 Jan 2000 02:45:39 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id CAA12765; Tue, 25 Jan 2000 02:45:17 -0500 (EST) To: Adriaan Joubert cc: pgsql-hackers@postgreSQL.org, pgsql-sql@postgreSQL.org Subject: Re: [HACKERS] DISTINCT ON: speak now or forever hold your peace In-reply-to: <388D4D9D.C4569FBC@albourne.com> References: <2295.948765015@sss.pgh.pa.us> <388D0D55.84F13203@bitmead.com> <11547.948771949@sss.pgh.pa.us> <388D4D9D.C4569FBC@albourne.com> Comments: In-reply-to Adriaan Joubert message dated "Tue, 25 Jan 2000 07:15:41 +0000" Date: Tue, 25 Jan 2000 02:45:17 -0500 Message-ID: <12762.948786317@sss.pgh.pa.us> From: Tom Lane Adriaan Joubert writes: > I've been using DISTINCT to fix things when vacuum gets into a mess (yes, it > happened again last night, > FATAL 1: VACUUM (vc_rpfheap): BlowawayRelationBuffers returned -2 > ). I then have loads of duplicates in a table and by doing a SELECT DISTINCT > ... INTO ... I can get rid of them. A few table renames later I'm back in > business. So how do I do this without DISTINCT? I didn't say anything about eliminating SELECT DISTINCT; I was talking about SELECT DISTINCT ON, which is a whole 'nother thing. > Better would be of course to get rid of the BlowawayRelationBuffers problem. Quite so. I think this is fixed for 7.0 ... that error message indicates a buffer refcount leak, and I fixed several problems along that line a couple months ago. We shall see if I got 'em all or not ... regards, tom lane