| From: | Emmanuel Cecchet <manu(at)frogthinker(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Locks on temp table and PREPARE |
| Date: | 2009-06-03 22:19:44 |
| Message-ID: | 4A26F700.7010205@frogthinker.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Emmanuel Cecchet <manu(at)frogthinker(dot)org> writes:
>
>> But when the transaction prepares, we know that. What would prevent us
>> to do at prepare time the same cleanup that commit does?
>>
>
> The entire point of PREPARE is that it's *not* committed yet.
>
Agreed but all objects that were created and dropped in the transaction
are going to be cleaned up whether the transaction commits or rollbacks.
It seems that releasing these resources at PREPARE time would help for
these 'temporary' objects that only have a transaction scope, right?
regards, manu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2009-06-03 22:22:29 | Re: Plan time Improvement - 64bit bitmapset |
| Previous Message | Oleg Bartunov | 2009-06-03 22:16:09 | Re: 8.4b2 tsearch2 strange error |