"Stefan Kaltenbrunner" <[EMAIL PROTECTED]> writes: > some additional datapoints: > > autovacuum on, delay 20: 8h 40min > autovacuum on, delay 0: 4h 23min
I realize this isn't directly addressing the problem but perhaps part of the solution would be to start advocating the use of pg_restore -1 ? That would solve the problem for the narrow case of pg_restore. In the long run we could think about exposing some kind of command for pg_restore to use which would disable autovacuum from touching a table. (Or take a session-level lock on the table -- shudder) -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---------------------------(end of broadcast)--------------------------- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
