| From: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ANALYZE locks pg_listener in EXCLUSIVE for long |
| Date: | 2004-05-03 03:35:18 |
| Message-ID: | 6.1.0.6.0.20040503132853.02fdc370@203.8.195.10 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At 12:45 PM 3/05/2004, Tom Lane wrote:
>Possibly we could reduce the strength of the lock taken by the async.c
>functions
If possible, this seems like a great option. We currently have a large
database with several hundred users who get locked out for as much as half
an hour while ANALYZE runs.
The data in the database is extremely dynamic, so the analyze needs to be
run regularly; we could run less often but this will just mean the problem
happens once per week instead of once per day.
Would ACCESS SHARE be OK?
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 03 5330 3172 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp.mit.edu:11371 |/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-05-03 03:46:09 | Re: ANALYZE locks pg_listener in EXCLUSIVE for long time? |
| Previous Message | Ted Kremenek | 2004-05-03 03:22:07 | Re: [CHECKER] 4 memory leaks in Postgresql 7.4.2 |