Re: Why not do distinct before SetOp - Mailing list pgsql-general

From David Rowley
Subject Re: Why not do distinct before SetOp
Date
Msg-id CAApHDvrXUuhGJ_rzsuLY3f1mou1w5RT4zxEb45gbBR3ap6vy4g@mail.gmail.com
Whole thread Raw
In response to Re: Why not do distinct before SetOp  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Wed, 6 Nov 2024 at 12:09, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Of course, I might be overestimating the performance benefit we'd get.
> But I'm tempted to give it a try.

I'm glad. I'm curious to see if you're right about the projection
overhead of the flags. If you're right, it seems like a not too
difficult optimisation to get in.

I like the idea as it also gets rid of the flag cruft from
prepunion.c, which saves having to add flags conditionally if
INTERCEPT/EXCEPT were ever made to use joins.

David



pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Why not do distinct before SetOp
Next
From: Dominique Devienne
Date:
Subject: About the stability of COPY BINARY data