pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: David G. Johnston <david.g.johnston@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: Andres Freund <andres@anarazel.de>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: transction_timestamp() inside of procedures
Date: Wed, 26 Sep 2018 11:11:27 -0300
Message-ID: <20180926141127.dvvkkms5gpuan3qc@alvherre.pgsql> (raw)
In-Reply-To: <20180926004739.GA15378@momjian.us>

On 2018-Sep-25, Bruce Momjian wrote:

> Well, it is an entire paragraph, so it might be too much.  If you
> download the zip file here:
> 
> 	http://www.wiscorp.com/sql200n.zip
> 
> and open 5CD2-02-Foundation-2006-01.pdf, at the top of page 289 under
> General Rules, paragraph label 3 has the description.  It talks about
> procedure statements and trigger functions, which seems promising.

I have the 2011 draft, not the 2006 one; you seem to be referring to
<datetime value function> (which is 6.32 in the 2011 draft I have).
General rule 3 is entirely unreadable, and is followed by this note:

  WG3:LCY-025 took no action on the preceding instance of general containment.
  It was felt that this rule is too complicated, to the point of being virtually
  unintelligible. In addition, the rule does not recognize that <datetime value
  function>s can be evaluated implicitly as <default option>s. It is believed
  that this rule does not reflect actual practice and should be rewritten to
  align it with implementations. Note that Subclause 15.1, “Effect of opening a
  cursor”, also has a General Rule on this subject. See
  Possible Problem FND-992 .

In SQL2016, this rule was removed completely.

I don't think this offers any practical guidance.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services




view thread (32+ messages)  latest in thread

Message-ID: <20180926141127.dvvkkms5gpuan3qc@alvherre.pgsql>
Permalink:  ../20180926141127.dvvkkms5gpuan3qc@alvherre.pgsql/
Also on:    postgresql.org/message-id/20180926141127.dvvkkms5gpuan3qc@alvherre.pgsql

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: alvherre@2ndquadrant.com, bruce@momjian.us, david.g.johnston@gmail.com, michael@paquier.xyz, andres@anarazel.de
  Subject: Re: transction_timestamp() inside of procedures
  In-Reply-To: <20180926141127.dvvkkms5gpuan3qc@alvherre.pgsql>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox