Postgres Pro
Downloads
Home   >   mailing lists

Re: [GENERAL] Vaccum Query - Mailing list pgsql-general

From Vik Fearing
Subject Re: [GENERAL] Vaccum Query
Date
Msg-id c9f77c03-3505-f377-da2f-d10e6b9a6804@2ndquadrant.com
Whole thread Raw
In response to [GENERAL] Vaccum Query  (PAWAN SHARMA <er.pawanshr0963@gmail.com>)
List pgsql-general
Tree view
On 05/04/2017 02:04 PM, PAWAN SHARMA wrote:
Hi All,

Any Idea what happens when we run standard vacuum (without full) on a table which has exclusive lock (or alter statement is being processed on that table).

What happens in this case ? Will vacuum wait for the alter to commit ?


Yes.

If so, how long ?


Either forever or for however long lock_timeout and/or statement_timeout are set to (or any user command like Ctrl+C).

If not, then what ?


If any of those limits are reached, the vacuum is cancelled.

And what actions can be taken to prevent this ?


Prevent what?  Even if the vacuum could run while the other transaction had the exclusive lock, it wouldn't be able to do any work.
-- 
Vik Fearing                                          +33 6 46 75 15 36
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support

pgsql-general by date:

Previous
From: Tony Finch
Date:
Subject: Re: [GENERAL] Can PG replace redis, amqp, s3 in the future?
Next
From: "Peter J. Holzer"
Date:
Subject: Re: [GENERAL] Caching and Blobs in PG? Was: Can PG replace redis,amqp, s3 in the future?