Horton

Re: SQL-standard function body

Peter Eisentraut <peter.eisentraut@enterprisedb.com>

View thread View on postgr.es
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Justin Pryzby <pryzby@telsasoft.com>, Jeff Janes <jeff.janes@gmail.com>
Cc: Julien Rouhaud <rjuju123@gmail.com>, Jaime Casanova <jcasanov@systemguards.com.ec>, pgsql-hackers@lists.postgresql.org
Date: 2021-04-29T07:14:22Z
Lists: pgsql-hackers 
On 27.04.21 04:44, Justin Pryzby wrote:
> On Thu, Apr 22, 2021 at 04:04:18PM -0400, Jeff Janes wrote:
>> This commit break line continuation prompts for unbalanced parentheses in
>> the psql binary.  Skimming through this thread, I don't see that this is
>> intentional or has been noticed before.
>>
>> with psql -X
>>
>> Before:
>>
>> jjanes=# asdf (
>> jjanes(#
>>
>> Now:
>>
>> jjanes=# asdf (
>> jjanes-#
>>
>> I've looked through the parts of the commit that change psql, but didn't
>> see an obvious culprit.
> 
> I haven't studied it in detail, but it probably needs something like this.

Yeah, fixed like that.

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