pgsql: Turns out that my recent elimination of the 'redundant' - Mailing list pgsql-committers

From tgl@svr1.postgresql.org (Tom Lane)
Subject pgsql: Turns out that my recent elimination of the 'redundant'
Date
Msg-id 20050423044254.6AF645339D@svr1.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Turns out that my recent elimination of the 'redundant' flatten_andors()
code in prepqual.c had a small drawback: the flatten_andors code was
able to cope with deeply nested AND/OR structures (like 10000 ORs in
a row), whereas eval_const_expressions tends to recurse until it
overruns the stack.  Revise eval_const_expressions so that it doesn't
choke on deeply nested ANDs or ORs.

Modified Files:
--------------
    pgsql/src/backend/optimizer/util:
        clauses.c (r1.195 -> r1.196)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/util/clauses.c.diff?r1=1.195&r2=1.196)

pgsql-committers by date:

Previous
From: "sandhya"
Date:
Subject: foot print for postgresq;
Next
From: tgl@svr1.postgresql.org (Tom Lane)
Date:
Subject: pgsql: int_aggregate's int_enum() doesn't work correctly with arrays