Re: [PATCH] Add native PIVOT syntax for SQL Server/Oracle compatibility

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: Myles Lewis <myles93(at)sbcglobal(dot)net>, pgsql-hackers(at)postgresql(dot)org, Vik Fearing <vik(at)postgresfriends(dot)org>
Subject: Re: [PATCH] Add native PIVOT syntax for SQL Server/Oracle compatibility
Date: 2025-11-27 00:35:43
Message-ID: aSec38dRZjLc1ARE@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 25, 2025 at 09:21:49PM +0100, Peter Eisentraut wrote:
> Your patch does not contain any documentation, so it's hard to tell what
> this is supposed to do if you don't already know those other products. Can
> you supply at least some informal documentation, and maybe some links to
> relevant documentation from those other products.

(Added Vik Fearing in CC.)

FWIW, I have very mixed feelings about the addition of clauses that
are not part of the SQL specifications AFAIK (just looked at my copy
of 2023), doing an implementation based on the argument of
compatibility that have been taken by other products here, because we
would have to live with this compatibility issues in the long-term.

Peter, Vik, is there an equivalent under discussion on the
specification side? If something gets released, an implementation may
make sense based on it, but at this stage it would hard to decide why
one direction would be more adapted than another.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2025-11-27 00:59:59 Re: Proposal: Conflict log history table for Logical Replication
Previous Message Michael Paquier 2025-11-27 00:24:20 Re: Consistently use palloc_object() and palloc_array()