[COMMITTERS] pgsql: Feature T401 is not listed in the SQL standard.

2008-10-22 Thread Peter Eisentraut
Log Message: --- Feature T401 is not listed in the SQL standard. Must have been a mistake. Modified Files: -- pgsql/src/backend/catalog: sql_features.txt (r1.24 -> r1.25) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/sql_features.txt?

[COMMITTERS] pgsql: When estimating without benefit of MCV lists (suggesting that one

2008-10-22 Thread Tom Lane
Log Message: --- When estimating without benefit of MCV lists (suggesting that one or both inputs is unique or nearly so), make eqjoinsel() clamp the ndistinct estimates to be not more than the estimated number of rows coming from the input relations. This allows the estimate to change in

[COMMITTERS] pgsql: Dept of better ideas: refrain from creating the planner's

2008-10-22 Thread Tom Lane
Log Message: --- Dept of better ideas: refrain from creating the planner's placeholder_list until vars are distributed to rels during query_planner() startup. We don't really need it before that, and not building it early has some advantages. First, we don't need to put it through the vari

[COMMITTERS] pgsql: Fix GiST's killing tuple: GISTScanOpaque->curpos wasn't

2008-10-22 Thread Teodor Sigaev
Log Message: --- Fix GiST's killing tuple: GISTScanOpaque->curpos wasn't correctly set. As result, killtuple() marks as dead wrong tuple on page. Bug was introduced by me while fixing possible duplicates during GiST index scan. Tags: REL8_1_STABLE Modified Files: --

[COMMITTERS] pgsql: Fix GiST's killing tuple: GISTScanOpaque->curpos wasn't

2008-10-22 Thread Teodor Sigaev
Log Message: --- Fix GiST's killing tuple: GISTScanOpaque->curpos wasn't correctly set. As result, killtuple() marks as dead wrong tuple on page. Bug was introduced by me while fixing possible duplicates during GiST index scan. Tags: REL8_2_STABLE Modified Files: --

[COMMITTERS] pgsql: Fix GiST's killing tuple: GISTScanOpaque->curpos wasn't

2008-10-22 Thread Teodor Sigaev
Log Message: --- Fix GiST's killing tuple: GISTScanOpaque->curpos wasn't correctly set. As result, killtuple() marks as dead wrong tuple on page. Bug was introduced by me while fixing possible duplicates during GiST index scan. Tags: REL8_3_STABLE Modified Files: --

[COMMITTERS] pgsql: Fix GiST's killing tuple: GISTScanOpaque->curpos wasn't

2008-10-22 Thread Teodor Sigaev
Log Message: --- Fix GiST's killing tuple: GISTScanOpaque->curpos wasn't correctly set. As result, killtuple() marks as dead wrong tuple on page. Bug was introduced by me while fixing possible duplicates during GiST index scan. Modified Files: -- pgsql/src/backend/access/

[COMMITTERS] pgsql: SQL:2008 alternative syntax for LIMIT/OFFSET: OFFSET num

2008-10-22 Thread Peter Eisentraut
Log Message: --- SQL:2008 alternative syntax for LIMIT/OFFSET: OFFSET num {ROW|ROWS} FETCH {FIRST|NEXT} [num] {ROW|ROWS} ONLY Modified Files: -- pgsql/doc/src/sgml/ref: select.sgml (r1.106 -> r1.107) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/s