Re: max_expr_depth

From: Ryan Mahoney <ryan(at)paymentalliance(dot)net>
To: Joseph Shraibman <jks(at)selectacast(dot)net>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: max_expr_depth
Date: 2001-06-18 19:59:03
Message-ID: 5.0.2.1.0.20010618205710.03d22460@paymentalliance.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I don't know the cause, but if you only have to run this procedure once in
a while, you could select all the records that need to be updated, and use
a text editor to build a few thousand single update statement, then save
this file and echo it to the postgres backend through psql.

Good Luck!

-r

At 08:50 PM 6/18/01 -0400, Joseph Shraibman wrote:

>I recently tried to do a big update with postgres 7.1.2. The update was
>something like
>UPDATE table SET status = 2 WHERE id IN (a few thousand entries) AND
>status = 1;
>
>
>and I got:
>ERROR: Expression too complex: nesting depth exceeds max_expr_depth =
>10000
>
>What exactly caused this and how do I work around it?
>
>
>--
>Joseph Shraibman
>jks(at)selectacast(dot)net
>Increase signal to noise ratio. http://www.targabot.com
>
>---------------------------(end of broadcast)---------------------------
>TIP 6: Have you searched our list archives?
>
>http://www.postgresql.org/search.mpl
>
>
>
>---
>Incoming mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com)
>Version: 6.0.251 / Virus Database: 124 - Release Date: 4/26/01

Attachment Content-Type Size
unknown_filename text/plain 166 bytes

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Thalis A. Kalfigopoulos 2001-06-18 19:59:56 embedded SQL cursos declare fails
Previous Message Tom Lane 2001-06-18 19:57:56 Re: ERROR: cache lookup for userid 26 failed