| From: | Rob Sargent <robjsargent(at)gmail(dot)com> |
|---|---|
| To: | Durgamahesh Manne <maheshpostgres9(at)gmail(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>, laurenz(dot)albe(at)cybertec(dot)at |
| Subject: | Re: Query optimization |
| Date: | 2025-03-14 02:49:04 |
| Message-ID: | 6072813E-9311-41CD-9987-89DD456098AC@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On Mar 13, 2025, at 8:39 PM, Durgamahesh Manne <maheshpostgres9(at)gmail(dot)com> wrote:
>
>
>
> On Fri, 14 Mar, 2025, 08:04 Rob Sargent, <robjsargent(at)gmail(dot)com <mailto:robjsargent(at)gmail(dot)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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2025-03-14 02:49:06 | Re: Query optimization |
| Previous Message | Durgamahesh Manne | 2025-03-14 02:39:46 | Re: Query optimization |