Re: enhance SPI to support EXECUTE commands

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Quan Zongliang <zongliang(dot)quan(at)postgresdata(dot)com>
Cc: Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: enhance SPI to support EXECUTE commands
Date: 2019-09-05 07:09:26
Message-ID: CAFj8pRAVT-eLKfCMr564RYcAsJoQtC22vqn-m5uAFCSFaLyXTg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

čt 5. 9. 2019 v 8:39 odesílatel Quan Zongliang <
zongliang(dot)quan(at)postgresdata(dot)com> napsal:

> Dear hackers,
>
> I found that such a statement would get 0 in PL/pgSQL.
>
> PREPARE smt_del(int) AS DELETE FROM t1;
> EXECUTE 'EXECUTE smt_del(100)';
> GET DIAGNOSTICS j = ROW_COUNT;
>
> In fact, this is a problem with SPI, it does not support getting result
> of the EXECUTE command. I made a little enhancement. Support for the
> number of rows processed when executing INSERT/UPDATE/DELETE statements
> dynamically.
>

Is there some use case for support this feature?

Regards

Pavel

> Regards,
> Quan Zongliang
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Etsuro Fujita 2019-09-05 07:10:44 Re: [HACKERS] advanced partition matching algorithm for partition-wise join
Previous Message Fujii Masao 2019-09-05 07:03:22 Re: pg_promote() can cause busy loop