| From: | Clodoaldo Pinto <clodoaldo(dot)pinto(at)gmail(dot)com> |
|---|---|
| To: | Michael Fuhr <mike(at)fuhr(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-general postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: update functions locking tables |
| Date: | 2005-08-30 13:01:53 |
| Message-ID: | a595de7a05083006016be6189@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
2005/8/30, Michael Fuhr <mike(at)fuhr(dot)org>:
>
> TRUNCATE acquires an AccessExclusiveLock, which conflicts with all
> other lock types. Locks are held until the transaction completes,
> so once this lock is acquired no other transactions will be able
> to access the table until this transaction commits or rolls back.
>
> DELETE is slower than TRUNCATE but it won't block readers in other
> transactions.
>
I think it is of great help. I will change it and let you know what happened.
Regards, Clodoaldo Pinto
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Antimon | 2005-08-30 13:05:45 | Php abstraction layers |
| Previous Message | Michael Fuhr | 2005-08-30 12:53:41 | Re: update functions locking tables |