Re: SPI isolation changes - Mailing list pgsql-hackers

From Tom Lane
Subject Re: SPI isolation changes
Date
Msg-id 1770512.1688143630@sss.pgh.pa.us
Whole thread Raw
In response to Re: SPI isolation changes  (Seino Yuki <seinoyu@oss.nttdata.com>)
Responses Re: SPI isolation changes
List pgsql-hackers
Seino Yuki <seinoyu@oss.nttdata.com> writes:
> Of course, executing SET TRANSACTION ISOLATION LEVEL with SPI_execute 
> will result in error.
> ---
> SPI_execute("SET TRANSACTION ISOLATION LEVEL SERIALIZABLE", false, 0);

> (Log Output)
> ERROR:  SET TRANSACTION ISOLATION LEVEL must be called before any query
> CONTEXT:  SQL statement "SET TRANSACTION ISOLATION LEVEL SERIALIZABLE"

Even if you just did SPI_commit?  That *should* fail if you just do
it right off the bat in a SPI-using procedure, because you're already
within the transaction that called the procedure.  But I think it
will work if you do SPI_commit followed by this SPI_execute.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Seino Yuki
Date:
Subject: Re: SPI isolation changes
Next
From: "Drouvot, Bertrand"
Date:
Subject: Re: ProcessStartupPacket(): database_name and user_name truncation