Re: behavior of GROUP BY with VOLATILE expressions

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Paul George <p(dot)a(dot)george19(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Richard Guo <guofenglinux(at)gmail(dot)com>
Subject: Re: behavior of GROUP BY with VOLATILE expressions
Date: 2024-07-19 14:47:48
Message-ID: CAKFQuwbhT143fVY6kGwO1+xEgkpJBnmnK3r7ABjLiiXNLgMXfw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jul 19, 2024 at 7:20 AM Paul George <p(dot)a(dot)george19(at)gmail(dot)com> wrote:

>
> I wanted to surface a discussion in [1] regarding the expected behavior of
> GROUP BY with VOLATILE expressions. There seems to be a discrepancy between
> how volatile functions (RANDOM(), also confirmed with TIMEOFDAY()) and
> subqueries are evaluated in groups. In the examples below, volatile
> functions do not always appear to be evaluated per-call (evidenced by
> looking at EXPLAIN or results) whereas scalar subqueries always appear to
> be independently evaluated.
>
> Based on the docs, "A query using a volatile function will re-evaluate
> the function at every row where its value is needed," it seems that the
> handling of subqueries is correct and that each call to RANDOM() should be
> evaluated (not the current behavior). But, what is correct/anticipated?
>
>
The observed behaviors are unlikely to change. Prior discussions can be
found regarding this:

https://www.postgresql.org/message-id/flat/CZHAF947QQQO.27MAUK2SVMBXW%40nmfay.com

David J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Junwang Zhao 2024-07-19 14:48:31 Re: Add new COPY option REJECT_LIMIT
Previous Message Jelte Fennema-Nio 2024-07-19 14:29:30 Re: Set log_lock_waits=on by default