Search Postgresql Archives

Re: transaction isolation level in plpgsql function

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: "Pavan Deolasee" <pavan.deolasee@xxxxxxxxx>
Subject: Re: transaction isolation level in plpgsql function
From: "Grzegorz Jaśkiewicz" <gryzman@xxxxxxxxx>
Date: Fri, 21 Nov 2008 09:49:37 +0000
Cc: "Sergey Moroz" <smo@xxxxxxxx>, pgsql-general@xxxxxxxxxxxxxx
In-reply-to: <2e78013d0811210120w50449b2cv6f07a2bbcc9516ef@xxxxxxxxxxxxxx>

whatever calls the function is responsible for transaction level change, because SELECT BLA(); already by default is wrapped by begin;end; - and you can only change transaction level right after BEGIN;
although , I feel your pain, it is not possible.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

References:
- transaction isolation level in plpgsql function
  - From: Sergey Moroz
- Re: transaction isolation level in plpgsql function
  - From: Pavan Deolasee

Prev by Date: Re: Postgres mail list traffic over time
Next by Date: Re: where in (select array)
Previous by thread: Re: transaction isolation level in plpgsql function
Next by thread: long vacuum full, gin index and unusually long delete
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux