[EMAIL PROTECTED] writes: > If anyone knows what may cause this problem, or has any other ideas, I > would be grateful.
Submit the command "VACUUM ANALYZE VERBOSE locations;" on both servers, and post the output of that. That might help us tell for sure whether the table is bloated (and needs VACUUM FULL/CLUSTER). The query plans are suggestive; on the 'master', the cost is 113921.40, whereas on the 'slave' it's 2185.09; I'll bet that those numbers are proportional to the number of pages assigned to the table on the respective servers... -- (reverse (concatenate 'string "ofni.sesabatadxunil" "@" "enworbbc")) http://cbbrowne.com/info/lsf.html "We use Linux for all our mission-critical applications. Having the source code means that we are not held hostage by anyone's support department." -- Russell Nelson, President of Crynwr Software ---------------------------(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
