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

Table lock on SET STATISTICS

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Table lock on SET STATISTICS
Date: 2004-09-23 18:59:20
Message-ID: 200409231159.20267.josh@agliodbs.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Folks,

Just noticed -- the hard way -- that running ALTER TABLE ... SET STATISTICS 
requires a full table lock.    I can't think of any practical reason why SET 
STATISTICS would need to lock the table; presumably this is just because it's 
an ALTER TABLE statement?    If so, maybe we should consider a method of SET 
STATISTICS which does not require a table lock?   The current functionality 
makes it very hard to test statistics levels on a production machine.

-- 
Josh Berkus
Aglio Database Solutions
San Francisco

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2004-09-23 19:52:35
Subject: Re: SQL-Invoked Procedures for 8.1
Previous:From: Josh BerkusDate: 2004-09-23 18:12:18
Subject: Re: SQL-Invoked Procedures for 8.1

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