Re: auto truncate/vacuum full
От | Alvaro Herrera |
---|---|
Тема | Re: auto truncate/vacuum full |
Дата | |
Msg-id | 20091027232939.GL4876@alvh.no-ip.org обсуждение исходный текст |
Ответ на | auto truncate/vacuum full (JC Praud <brutaltruth42@gmail.com>) |
Ответы |
Re: auto truncate/vacuum full
Re: auto truncate/vacuum full |
Список | pgsql-general |
JC Praud escribió: > - Last night the database locked. pg_log full of messages about insert into > the mother table waiting for a lock. This bit does not make much sense to me. A transaction waiting will not show up in the log. Were they cancelled? Can you paste an extract from the log? > - After about 40min, the waiting queries acquired their locks and ran. Do you have a vacuum in cron or something like that? As Tom says, if it had been autovacuum, it should have been cancelled automatically (else we've got a bug); but something invoking vacuum externally wouldn't have, so what you describe is what we would expect. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support
В списке pgsql-general по дате отправления: