[snip] > Yes, but it could be a disk issue because you're doing more work than > you need to. If your UPDATEs are chasing down a lot of dead tuples, > for instance, you'll peg your I/O even though you ought to have I/O > to burn.
OK, this sounds interesting, but I don't understand: why would an update "chase down a lot of dead tuples" ? Should I read up on some docs, cause I obviously don't know enough about how updates work on postgres... And how would the analyze help in finding this out ? I thought it would only show me additionally the actual timings, not more detail in what was done... Thanks, Csaba. ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly