Received: from post.mail.demon.net (post-10.mail.demon.net [194.217.242.39])
	by hub.org (8.8.8/8.7.5) with SMTP id KAA06902 for
	<pgsql-sql@postgresql.org>; Sat, 16 May 1998 10:07:36 -0400 (EDT)
Received: from cenderis.demon.co.uk ([193.237.0.193]) by post.mail.demon.net
	id aa1016207; 16 May 98 14:05 GMT
Received: (from bruce@localhost)
	by cenderis.demon.co.uk (8.8.7/8.8.7) id PAA01333;
	Sat, 16 May 1998 15:02:19 +0100
To: pgsql-sql@postgresql.org
Subject: Re: [SQL] Duplicate rows
References: <Pine.LNX.3.95.980516081545.14769B-100000@shell.mpsi.net>
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=US-ASCII
From: Bruce Stephens <bruce@cenderis.demon.co.uk>
Date: 16 May 1998 15:02:11 +0100
In-Reply-To: Andy Lewis's message of "Sat, 16 May 1998 08:18:05 -0500 (CDT)"
Message-ID: <m3wwbme2l8.fsf@cenderis.demon.co.uk>
X-Mailer: Gnus v5.6.9/XEmacs 20.4 - "Emerald"
Lines: 14

Andy Lewis <alewis@mpsi.net> writes:

> Right, I know that there are dups in the column. But, I don't know
> where they are nor do I know their value(s). I want to be able to
> find, say, two interger values that are in the same column but,
> different rows.

How about

SELECT t1.col,t1.oid, t2.oid FROM fred AS t1, fred AS t2 
	WHERE t1.col=t2.col AND t1.oid<t2.oid

(I haven't tested this, but it's the right kind of idea: select the
interesting bits from a self-join.)