This is a discussion on pgsql: Fix for COPY-after-truncate feature. within the pgsql Committers forums, part of the PostgreSQL category; --> Log Message: ----------- Fix for COPY-after-truncate feature. Simon Riggs Modified Files: -------------- pgsql/src/backend/catalog: index.c (r1.279 -> r1.280) ( http://developer.postgresql.org/cvsw...1.279&r2=1.280 ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Log Message: ----------- Fix for COPY-after-truncate feature. Simon Riggs Modified Files: -------------- pgsql/src/backend/catalog: index.c (r1.279 -> r1.280) (http://developer.postgresql.org/cvsw...1.279&r2=1.280) pgsql/src/backend/utils/cache: relcache.c (r1.256 -> r1.257) (http://developer.postgresql.org/cvsw...1.256&r2=1.257) pgsql/src/include/utils: relcache.h (r1.57 -> r1.58) (http://developer.postgresql.org/cvsw...1=1.57&r2=1.58) ---------------------------(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 | |
|
|