Re: Re: About the return states of SPI_execute for plpy.execute().status()

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Euler Taveira" <euler(at)eulerto(dot)com>
Cc: arturocuya099(at)gmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: Re: About the return states of SPI_execute for plpy.execute().status()
Date: 2021-02-17 19:58:47
Message-ID: 2743963.1613591927@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

"Euler Taveira" <euler(at)eulerto(dot)com> writes:
> It is referring to the SPI_execute() return values [1] whose mapped integers
> are available in [2]. 11 refers to INSERT ... RETURNING. Maybe PL/Python should
> expose these SPI constants too (if it doesn't).

I wouldn't be in too much of a hurry to do that, because there's been
repeated discussion of removing (or at least obsoleting) most of those
codes in favor of throwing regular errors for the cases that represent
error conditions. Better to wait to change plpython until after that
dust settles.

regards, tom lane

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Jordi Gutiérrez Hermoso 2021-02-17 20:08:35 Document target_role param of ALTER DEFAULT PRIVILEGES
Previous Message Euler Taveira 2021-02-17 19:43:58 Re: About the return states of SPI_execute for plpy.execute().status()