| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Jan Wieck <JanWieck(at)yahoo(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Lock problem with autovacuum truncating heap |
| Date: | 2011-03-27 22:21:20 |
| Message-ID: | AANLkTiky9fSGoZF+kbk_xgLUWVr3qC3PrgqKKESU+MZh@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Mar 27, 2011 at 3:25 PM, Jan Wieck <JanWieck(at)yahoo(dot)com> wrote:
> Since we are talking about stable releases, I think just releasing and
> reacquiring the exclusive lock is enough. We can then try to further improve
> things for future releases.
That seems unsafe - things can change under you while you don't hold the lock...
I kind of like the idea of committing the transaction and then
beginning a new one just to do the truncation. Given the way the
deadlock detector treats autovacuum, the current coding seems quite
risky.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-03-27 22:27:34 | Re: Additional options for Sync Replication |
| Previous Message | Greg Stark | 2011-03-27 22:06:34 | Re: Lock problem with autovacuum truncating heap |