From: Pierre-Frédéric Caillaud <lists@boutiquenumerique.com>
To: Ellert van Koperen <ellert@vankoperen.nl>
To: PostgreSQL <pgsql-sql@postgresql.org>
Subject: Re: Making dirty reads possible?
Date: Tue, 07 Dec 2004 09:27:41 +0100
Message-ID: <opsimpsfcmcq72hf@musicbox> (raw)
In-Reply-To: <41B34A08.1070603@vankoperen.nl>
References: <20041201215811.476CF23CE8@ws5-3.us4.outblaze.com>
<20041201234311.L622@hermes.hilbert.loc>
<Pine.NEB.4.60.0412042310560.7853@dab.cs.stevens-tech.edu>
<41B34A08.1070603@vankoperen.nl>
You can always use contribs/dblink, or a plperlu/plpythonu function which
writes to a file...
> So, summarising:
> - Nested transactions is not (yet) supported
> - READ UNCOMMITTED isolation level is not (yet) supported
> - EXECUTE does not circumvent the transaction
>
> Is there a way around this?
>
> Regards,
> Ellert.
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
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: pgsql-sql@postgresql.org
Cc: lists@boutiquenumerique.com, ellert@vankoperen.nl
Subject: Re: Making dirty reads possible?
In-Reply-To: <opsimpsfcmcq72hf@musicbox>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox