| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Analyze using savepoints? |
| Date: | 2004-08-09 14:33:43 |
| Message-ID: | 14528.1092062023@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
> I read this in the release notes:
> ---
> # Database-wide ANALYZE does not hold locks across tables (Tom)
> This reduces the potential for deadlocks against other backends that
> want exclusive locks on tables. To get the benefit of this change, do
> not execute database-wide ANALYZE inside a transaction block (BEGIN
> block); it must be able to commit and start a new transaction for each
> table.
> ---
> Does that mean that now if we used savepoints internally, analyze can
> still be run in a transaction and still not hold lots of locks?
No.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2004-08-09 14:35:04 | Re: Ready for Beta ... ? |
| Previous Message | Tom Lane | 2004-08-09 14:32:54 | Re: Changing the type of timestamp columns |