Re: transction_timestamp() inside of procedures

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: transction_timestamp() inside of procedures
Date: 2018-09-21 04:55:36
Message-ID: 20180921045536.GJ1338@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Sep 20, 2018 at 07:40:40PM -0400, Bruce Momjian wrote:
> This surprised me since I expected a new timestamp after commit. Is
> this something we want to change or document? Are there other
> per-transaction behaviors we should adjust?

I don't quite follow your argument here. clock_timestamp is known to be
volatile, while the two others are stable, so its value can change
within a transaction.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2018-09-21 05:12:06 Re: transction_timestamp() inside of procedures
Previous Message Michael Paquier 2018-09-21 04:53:16 Re: pgsql: Make WAL segment size configurable at initdb time.