From: Tom Lane <tgl@sss.pgh.pa.us>
To: sanskar@flintk12.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18607: UNION ALL discards all foreign key relations +
 indexes
In-reply-to: <18607-651aa996c1e71d48@postgresql.org>
References: <18607-651aa996c1e71d48@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Mon, 09 Sep 2024 15:16:33 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3208237.1725899380.1@sss.pgh.pa.us>
Date: Mon, 09 Sep 2024 12:29:40 -0400
Message-ID: <3208238.1725899380@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3208238.1725899380%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> CREATE OR REPLACE VIEW v3.temp_view AS
> SELECT * FROM users WHERE id = 'e-1'
> UNION ALL
> SELECT * FROM users WHERE id = 'e-2';

> Either way when the view is created, the indexes and the related relations
> of the foreign key references are being dropped. 

Views do not have either indexes or foreign keys.

> What + Why? I am processing the result of the union in another CTE which now
> is not having access to indices and so it is performing a seq scan!

This seems to be a performance complaint, rather than a valid bug
report.  You might find it helpful to read

https://wiki.postgresql.org/wiki/Slow_Query_Questions

			regards, tom lane