agora inbox for [email protected]
help / color / mirror / Atom feedFrom: Emmanuel Cecchet <[email protected]>
To: Tom Lane <[email protected]>
Cc: Heikki Linnakangas <[email protected]>
Cc: [email protected]
Subject: Re: Transactions and temp tables
Date: Wed, 08 Oct 2008 09:55:14 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
Tom Lane wrote:
> Emmanuel Cecchet <[email protected]> writes:
>
>> Thanks for the example, I get it now. Does it make sense to allow any
>> request execution between PREPARE TRANSACTION and the subsequent COMMIT
>> or ROLLBACK?
>>
>
> Yes. Don't even think of trying to disallow that. The COMMIT doesn't
> even have to happen in the same session, anyway.
>
Ok, so actually I don't see any different behavior between a temp table
or a regular table. The locking happens the same way and as long as the
commit prepared happens (potentially in another session), the lock is
released at commit time which seems to make sense.
The issue that Heikki was mentioning about the server not shutting down
seems to happen as soon as you have a single transaction that has
prepared commit but not commit/rollback yet. This seems also independent
of whether you are using a temp table or not.
It seems that the patch did not alter the behavior of PG in that regard.
What do you think?
Emmanuel
view thread (37+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Transactions and temp tables
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox