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 >[EMAIL PROTECTED] >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
--- Outgoing 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
---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster