| From: | Doug McNaught <doug(at)wireboard(dot)com> |
|---|---|
| To: | Joseph Shraibman <jks(at)selectacast(dot)net> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: max_expr_depth |
| Date: | 2001-06-19 00:59:47 |
| Message-ID: | m3vgltb7y4.fsf@belphigor.mcnaught.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Joseph Shraibman <jks(at)selectacast(dot)net> writes:
> 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
Most likely your IN clause is too big. Try loading those few thousand
entries into a temporary table and doing a join.
-Doug
--
The rain man gave me two cures; he said jump right in,
The first was Texas medicine--the second was just railroad gin,
And like a fool I mixed them, and it strangled up my mind,
Now people just get uglier, and I got no sense of time... --Dylan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joseph Shraibman | 2001-06-19 01:15:55 | Re: max_expr_depth |
| Previous Message | Joseph Shraibman | 2001-06-19 00:50:49 | max_expr_depth |