On Thu, 23 Jun 2005, Simon Riggs wrote:
That was the bit I didn't. Fix partially implemented and I am to submit for 8.1, godspeed my typing fingers. There's a simple workaround if you have a low transaction rate system: load up enough data to trip into the next xlog.
I just noticed one other thing...it will always look in the pg_xlog directory for that current xlog which is required and will not look for it in the archive dir. It would be nice if it would also look in the archive dir for this one, no?
-- Jeff Frost, Owner <[EMAIL PROTECTED]> Frost Consulting, LLC http://www.frostconsultingllc.com/ Phone: 650-780-7908 FAX: 650-649-1954 ---------------------------(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
