Re: Doubt about AccessExclusiveLock in ALTER TABLE .. SET ( .. );

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Fabrízio Mello <fabriziomello(at)gmail(dot)com>
Cc: Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Doubt about AccessExclusiveLock in ALTER TABLE .. SET ( .. );
Date: 2015-03-31 17:17:03
Message-ID: CA+TgmoZyBp8rnWimAdCQoquZhaP=jBJDfane6QsrFqowTgWwjA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Mar 31, 2015 at 9:11 AM, Fabrízio de Royes Mello
<fabriziomello(at)gmail(dot)com> wrote:
> Attached a very WIP patch to reduce lock level when setting autovacuum
> reloptions in "ALTER TABLE .. SET ( .. )" statement.

I think the first thing we need to here is analyze all of the options
and determine what the appropriate lock level is for each, and why.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Janes 2015-03-31 17:18:12 Re: vac truncation scan problems
Previous Message Abhijit Menon-Sen 2015-03-31 17:13:49 Re: a fast bloat measurement tool (was Re: Measuring relation free space)