Re: Should we introduce a "really strict" volatility about return values?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Should we introduce a "really strict" volatility about return values?
Date: 2018-01-26 14:46:20
Message-ID: CA+TgmobUfQHi3GFcgVnm+aZ-NF0T+xqu+0D9j3GyBMfdA4XfGg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jan 25, 2018 at 6:51 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> I don't plan to work on this anytime soon, but I though it's interesting
> enough to put out there and see what others think.

I mean, if it buys enough performance, it's probably worth doing.
Sort of annoying to have to introduce more syntax, but it could be
worth it.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2018-01-26 14:49:12 Re: \describe*
Previous Message Michael Paquier 2018-01-26 14:13:54 Updating timezone data to 2018c