From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
---|---|
To: | seth(dot)m(dot)green(at)gmail(dot)com |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: ACCESS EXCLUSIVE LOCK |
Date: | 2006-03-05 23:28:29 |
Message-ID: | 20060305232829.GF80721@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Thu, Mar 02, 2006 at 06:16:00AM -0800, seth(dot)m(dot)green(at)gmail(dot)com wrote:
> > TRUNCATE is another command that takes an access exclusive lock.
>
> The whole SP takes about 10 seconds to run total. The TRUNCATE command
> only takes less than a second. However, the access exclusive lock is
> held throughout the entire SP, not just during the execution of the
> TRUNCATE command. Shouldn't TRUNCATE be releasing the lock as soon as
> it finishes?
Nope. Locks stick around until the transaction finishes.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2006-03-05 23:34:24 | Re: Not so happy with psql's new multiline behavior |
Previous Message | Bruce Momjian | 2006-03-05 21:09:53 | Re: Remove vestigial UNION JOIN support? |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-03-06 02:09:36 | Re: LDAP auth |
Previous Message | Neil Conway | 2006-03-05 21:38:45 | Re: reorder GROUP BY list |