Skip site navigation (1) Skip section navigation (2)

Re: VACUUM FULL deadlock with backend startup

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Nikhil Sontakke <nikhil(dot)sontakke(at)enterprisedb(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: VACUUM FULL deadlock with backend startup
Date: 2011-03-20 03:15:10
Message-ID: AANLkTikTwk+dAQ7oVngPJVNwZQZbM8=PPXzZr5jCx4QL@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Sat, Mar 19, 2011 at 10:46 AM, Nikhil Sontakke
<nikhil(dot)sontakke(at)enterprisedb(dot)com> wrote:
> Not really a performance issue AFAICS. If the relcache init file exists,
> then the phase2 of the catalog cache which eventually calls the above code
> path is avoided.

Oh, that doesn't sound so bad, then.

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

In response to

Responses

pgsql-hackers by date

Next:From: homDate: 2011-03-20 03:50:01
Subject: Re: I am confused after reading codes of PostgreSQL three week
Previous:From: Tom LaneDate: 2011-03-19 21:22:39
Subject: WIP patch: collation assignment algorithm rewrite

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group