This is a discussion on pgsql: Add an ORDER BY to nail down the expected row order from a query within the pgsql Committers forums, part of the PostgreSQL category; --> Log Message: ----------- Add an ORDER BY to nail down the expected row order from a query that's been ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Log Message: ----------- Add an ORDER BY to nail down the expected row order from a query that's been shown to be sensitive to concurrent autovacuum. Per Alvaro. Modified Files: -------------- pgsql/src/test/regress/sql: cluster.sql (r1.11 -> r1.12) (http://developer.postgresql.org/cvsw...1=1.11&r2=1.12) pgsql/src/test/regress/expected: cluster.out (r1.19 -> r1.20) (http://developer.postgresql.org/cvsw...1=1.19&r2=1.20) ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match |
| Thread Tools | |
| Display Modes | |
|
|