Alvaro Herrera <[EMAIL PROTECTED]> writes: > Each worker, including the initial one, starts vacuuming tables > according to pgstat data. They recheck the pgstat data after finishing > each table, so that a table vacuumed by another worker is not processed > twice (maybe problematic: a table with high update rate may be vacuumed > more than once. Maybe this is a feature not a bug).
How are you going to make that work without race conditions? ISTM practically guaranteed that all the workers will try to vacuum the same table. > Once autovacuum_naptime has passed, if the workers have not finished > yet, the launcher wants to vacuum another database. This seems a rather strange design, as it will encourage concentrations of workers in a single database. Wouldn't it be better to spread them out among multiple databases by default? regards, tom lane ---------------------------(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