Re: SPI isolation changes

From: Seino Yuki <seinoyu(at)oss(dot)nttdata(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: SPI isolation changes
Date: 2023-07-01 11:31:39
Message-ID: 0cae650bcf9ac49a43ae975d37eb203f@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2023-07-01 01:47, Tom Lane wrote:
> Seino Yuki <seinoyu(at)oss(dot)nttdata(dot)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

I'm sorry. I understood wrongly.
SPI_execute(SET TRANSACTION ISOLATION LEVEL ~ ) after executing
SPI_commit succeeded.

Thank you. My problem is solved.

Regards,
--
Seino Yuki
NTT DATA CORPORATION

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dean Rasheed 2023-07-01 12:33:40 Re: MERGE ... WHEN NOT MATCHED BY SOURCE
Previous Message Dean Rasheed 2023-07-01 11:07:42 Re: MERGE ... RETURNING