Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
pgsql: In a nestloop inner indexscan, it's OK to use pushed-down
- From: tgl(at)postgresql(dot)org (Tom Lane)
- To: pgsql-committers(at)postgresql(dot)org
- Subject: pgsql: In a nestloop inner indexscan, it's OK to use pushed-down
- Date: Tue, 6 Dec 2005 12:50:38 -0400 (AST)
- Message-id: <20051206165038.1017F9DD55A@postgresql.org> <text/plain>
Log Message:
-----------
In a nestloop inner indexscan, it's OK to use pushed-down baserestrictinfo
clauses even if it's an outer join. This is a corner case since such
clauses could only arise from weird OUTER JOIN ON conditions, but worth
fixing. Per example from Ron at cheapcomplexdevices.com.
Modified Files:
--------------
pgsql/src/backend/optimizer/path:
indxpath.c (r1.195 -> r1.196)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/indxpath.c.diff?r1=1.195&r2=1.196)
- Prev by Date: npgsql - Npgsql: 2005-12-06 Francisco Figueiredo Jr.
- Next by Date: pgsql: In a nestloop inner indexscan, it's OK to use pushed-down
- Previous by thread: mysqlcompat - mysqlcompat: Add the misc functions: inet_ntoa, inet_aton
- Next by thread: pgsql: In a nestloop inner indexscan, it's OK to use pushed-down
- Indexes: