From: Rod Taylor <rbt@rbt.ca>
To: markus brosch <brosch@gmx.de>
Cc: mallah@trade-india.com, pgsql-sql <pgsql-sql@postgresql.org>
Subject: Re: max length of sql select statement ?
Date: 09 Jul 2003 13:29:58 +0000
Message-ID: <1057757398.46100.63.camel@jester> (raw)
In-Reply-To: <1057743944.15655.12.camel@sam>
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>
<1057743944.15655.12.camel@sam>
> Maybe we can disuss that problem here again?! What exactly means
> "max_expr_depth"? Thanks for any help
If I'm not mistaken, max_expr_depth is used to catch runaway recursion
(view a is select * from b, view b is select * from a).
It's a tunable in postgresql.conf. Toss a couple of 0's behind the
number and uncomment the line.
Attachments:
signature.asc (application/pgp-signature, 186B) download
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: rbt@rbt.ca, brosch@gmx.de
Subject: Re: max length of sql select statement ?
In-Reply-To: <1057757398.46100.63.camel@jester>
* 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