X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (developer.postgresql.org [64.117.224.193]) by svr1.postgresql.org (Postfix) with ESMTP id 9BF41B43161 for ; Wed, 9 Jul 2003 09:50:10 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr1.postgresql.org [64.117.224.193]) (amavisd-new, port 10024) with ESMTP id 16913-08 for ; Wed, 9 Jul 2003 06:49:41 -0300 (ADT) Received: from mail.bgm-gmbh.de (gamma.bgm-hosting.de [217.115.144.90]) by svr1.postgresql.org (Postfix) with ESMTP id 0BEAAB43183 for ; Wed, 9 Jul 2003 06:49:41 -0300 (ADT) Received: from bgm-gmbh.de (localhost [127.0.0.1]) by mail.bgm-gmbh.de (Postfix) with ESMTP id 80568B614F; Wed, 9 Jul 2003 11:49:42 +0200 (CEST) Received: from . (pD9E8EEE9.dip.t-dialin.net [217.232.238.233]) by mail.bgm-gmbh.de (Postfix) with ESMTP id 195BEB5A05; Wed, 9 Jul 2003 11:49:41 +0200 (CEST) Subject: Re: max length of sql select statement ? From: markus brosch To: Rod Taylor Cc: mallah@trade-india.com, pgsql-sql In-Reply-To: <1057594852.46100.11.camel@jester> References: <1057592658.881.93.camel@sam> <1101.219.65.226.199.1057593454.squirrel@mail.trade-india.com> <1057594050.886.104.camel@sam> <1057594852.46100.11.camel@jester> Content-Type: text/plain Organization: Message-Id: <1057743944.15655.12.camel@sam> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 09 Jul 2003 11:45:44 +0200 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS perl-11 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200307/100 X-Sequence-Number: 14214 On Mon, 2003-07-07 at 18:20, Rod Taylor wrote: > > Could be a solution?! > > The question is - how long could the IN be? > > I'm not sure about IN specifically, but I know you can do: > SELECT * FROM table WHERE col = '<1GB long file>'; > It tends not to be friendly for Ram though :) Hi again! After I decided to use this statement (discussion two days ago!): SELECT * FROM table WHERE columnX IN ('a', 'b', 'c', 'd', 'e', ... ); I got this error :-((( java.sql.SQLException: ERROR: Expression too complex: nesting depth exceeds max_expr_depth = 10000 I was searching the web and only found this discussion: http://groups.google.de/groups?hl=de&lr=&ie=UTF-8&oe=UTF-8&threadm=3B2EA1E9.843D940A%40selectacast.net&rnum=1&prev=/groups%3Fhl%3Dde%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26q%3DExpression%2Btoo%2Bcomplex%253A%2Bnesting%2Bdepth%2Bexceeds%2Bmax_expr_depth%2B%253D%2B10000%26btnG%3DGoogle%2BSuche Maybe we can disuss that problem here again?! What exactly means "max_expr_depth"? Thanks for any help Cheers Markus