Re: Second RewriteQuery complains about first RewriteQuery in edge case

From: Bernice Southey <bernice(dot)southey(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Kirill Reshke <reshkekirill(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Second RewriteQuery complains about first RewriteQuery in edge case
Date: 2025-11-26 20:28:33
Message-ID: CAEDh4nwOuB4X3Ysxc6qUyXh4D8eEEFEFLQnG7FuEmVstiCiuFg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bernice Southey <bernice(dot)southey(at)gmail(dot)com> wrote:
> I went through the history and it seemed to me the repeat rewrite was
> accidental because of the two ways this method can recurse.
I mean the repeat rewrite of the cteList was accidental, not the
repeat rewrite of views. I couldn't think why a view would mean a
cteList needed re-rewriting, but I know very little about view rules.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Myles Lewis 2025-11-26 20:39:40 Re: [PATCH] Add native PIVOT syntax for SQL Server/Oracle compatibility
Previous Message Myles Lewis 2025-11-26 20:26:14 Re: [PATCH] contrib: Add pg_datemath extension with datediff function