Re: Q on SELECT column list pushdown from view to table

From: Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Q on SELECT column list pushdown from view to table
Date: 2025-03-26 21:14:29
Message-ID: Z-RuNb6EgVha2qOA@hermes.hilbert.loc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Am Wed, Mar 26, 2025 at 04:36:55PM -0400 schrieb Tom Lane:

> It is intentional that this happens even if the reference to
> private_col is subsequently optimized away. To do otherwise
> would make implementation artifacts in the optimizer far too
> visible, and there's also a very strong case that it would
> violate the SQL standard.

That's what I wanted to know.

Thanks,
Karsten
--
GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Alexandru Lazarev 2025-03-26 21:17:00 Re: Is pg_basebackup Performance Limited by Files Page Cache?
Previous Message Tom Lane 2025-03-26 20:36:55 Re: Q on SELECT column list pushdown from view to table