Re: Making dirty reads possible? - Mailing list pgsql-sql

From Pierre-Frédéric Caillaud
Subject Re: Making dirty reads possible?
Date
Msg-id opsimpsfcmcq72hf@musicbox
Whole thread Raw
In response to Making dirty reads possible?  (Ellert van Koperen <ellert@vankoperen.nl>)
List pgsql-sql
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
>




pgsql-sql by date:

Previous
From: "Paulo Assis"
Date:
Subject: Postgesql 8 beta 5: ecpg and date type - Access violations
Next
From: Christoph Haller
Date:
Subject: Unresolved external: tgetent