Re: SQL-standard function body

Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Julien Rouhaud <rjuju123@gmail.com>
Cc: Jaime Casanova <jcasanov@systemguards.com.ec>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-04-07T19:55:40Z
Lists: pgsql-hackers
On 03.04.21 05:39, Julien Rouhaud wrote:
> Are you planning to run pg_indent before committing or would that add too much
> noise?

Yeah, I figured I'd leave that for later, to not bloat the patch so much.

> Anyway since it's only stylistic issues and the feature freeze is getting
> closer I'm marking the patch as ready for committer.

Committed.  Thanks!



Commits

  1. Don't crash on empty statements in SQL-standard function bodies.

  2. psql: Fix line continuation prompts for unbalanced parentheses

  3. Provide query source text when parsing a SQL-standard function body.

  4. Revert "Cope with NULL query string in ExecInitParallelPlan()."

  5. Undo decision to allow pg_proc.prosrc to be NULL.

  6. SQL-standard function body

  7. Move pg_stat_statements query jumbling to core.

  8. Extend SQL function tests lightly