Re: DROP and ddl_command_end.

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: DROP and ddl_command_end.
Date: 2020-03-09 17:29:47
Message-ID: CA+TgmoaxYQ8=S00Ui-res6gTx5Bt9SD0yYpQKFcRC-BA_JgqoA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Mar 9, 2020 at 3:54 AM Kyotaro Horiguchi
<horikyota(dot)ntt(at)gmail(dot)com> wrote:
> I may be missing something, andt any opinions, thoughts or suggestions
> are welcome.

Since it's a set-returning function, I would have expected that
instead of trying to assign the result to a variable, you'd loop over
it using FOR var IN query.

But if that's the problem, the error message is a bit odd.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2020-03-09 17:33:55 Re: explain HashAggregate to report bucket and memory stats
Previous Message Robert Haas 2020-03-09 17:27:20 Re: recovery_target_action=pause with confusing hint