Re: Query optimization

Rob Sargent <robjsargent@gmail.com>

From: Rob Sargent <robjsargent@gmail.com>

To: Durgamahesh Manne <maheshpostgres9@gmail.com>

Cc: Adrian Klaver <adrian.klaver@aklaver.com>, pgsql-general <pgsql-general@lists.postgresql.org>, laurenz.albe@cybertec.at

Date: 2025-03-14T02:49:04Z

Lists: pgsql-general

> On Mar 13, 2025, at 8:39 PM, Durgamahesh Manne <maheshpostgres9@gmail.com> wrote:
> 
> 
> 
> On Fri, 14 Mar, 2025, 08:04 Rob Sargent, <robjsargent@gmail.com <mailto:robjsargent@gmail.com>> wrote:
> 
> Hi
> 
> Gave you plan with out limit . Stats up to date insert .....on conflict do nothing runs some times 
> 
> Regards 
> Durga Mahesh
> 
> 

But still using the “select exists”, thereby turning the result into a true/false value?  I do not follow your point on the usage of “on conflict”.  Is this also something whose behaviour has changed recently?  I assume it references the same table as the original sql?