Re: 2019-03 CF Summary / Review - Tranche #2 - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: 2019-03 CF Summary / Review - Tranche #2
Date
Msg-id CAFj8pRBf9oGJKiTo=9AG2zj3LZ_LM-8B67NWPfc_BCis+WoDQg@mail.gmail.com
Whole thread Raw
In response to Re: 2019-03 CF Summary / Review - Tranche #2  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Hi

 
- block level PRAGMA

  NR: My reading of this thread is that the proposal is closer to being
  rejected than merged.

  Andres: reject or punt?


This patch is very simple and has strong sense for users of plpgsql_checks.  For first moment, only plpgsql_check's users can get some advance from it. But if we implement autonomous transactions, and I hope so this feature will be implemented, then this code can be used for Oracle's PL/SQL syntax compatible implementation. There is not any disadvantage - it is clean, and compatible with ADA, PL/SQL .. I implemented just only block level PRAGMA, and there was not any disagreement.

Regards

Pavel

pgsql-hackers by date:

Previous
From: Arseny Sher
Date:
Subject: Re: Too rigorous assert in reorderbuffer.c
Next
From: Peter Geoghegan
Date:
Subject: Re: 2019-03 CF Summary / Review - Tranche #2