pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: markus brosch <brosch@gmx.de>
To: Rod Taylor <rbt@rbt.ca>
Cc: mallah@trade-india.com, pgsql-sql <pgsql-sql@postgresql.org>
Subject: Re: max length of sql select statement ?
Date: 09 Jul 2003 11:45:44 +0200
Message-ID: <1057743944.15655.12.camel@sam> (raw)
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>

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...

Maybe we can disuss that problem here again?! What exactly means
"max_expr_depth"? Thanks for any help
Cheers Markus





view thread (14+ messages)  latest in thread

Message-ID: <1057743944.15655.12.camel@sam>
Permalink:  ../1057743944.15655.12.camel@sam/
Also on:    postgresql.org/message-id/1057743944.15655.12.camel@sam

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: brosch@gmx.de, rbt@rbt.ca
  Subject: Re: max length of sql select statement ?
  In-Reply-To: <1057743944.15655.12.camel@sam>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox