Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eBHIhF616954 for ; Sun, 17 Dec 2000 13:43:15 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id eBHIhTL21197; Sun, 17 Dec 2000 13:43:29 -0500 (EST) To: Frank Joerdens cc: pgsql-sql@postgresql.org Subject: Re: Subqueries in Non-SELECT Queries In-reply-to: <3A3CFFF9.3615E576@joerdens.de> References: <3A3CFFF9.3615E576@joerdens.de> Comments: In-reply-to Frank Joerdens message dated "Sun, 17 Dec 2000 19:03:37 +0100" Date: Sun, 17 Dec 2000 13:43:28 -0500 Message-ID: <21194.977078608@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200012/186 X-Sequence-Number: 520 Frank Joerdens writes: > mpi=# update index set level = 2 where parentid = ( select id from > index where level = 1 ); > ERROR: More than one tuple returned by a subselect used as an expression. Apparently the subquery "select id from index where level = 1" is returning more than one row. Perhaps you want WHERE parentid IN subselect rather than WHERE parentid = subselect. "=" is a scalar operator, not a set operator. regards, tom lane