[kdepim-users] akonadi fsck fails

[Pablo Sanchez]

[ Comments below, in-line ]


On 08/26/2015 03:19 PM, J. Roeleveld wrote:
> Based on that, the following one is the best option:
> ++++
> delete from pimitemflagrelation
>   where pimitemflagrelation.pimitem_id in (
>             select pimitem_id
>             from pimitemflagrelation
>             left join pimitemtable
>               on pimitemflagrelation.pimitem_id = pimitemtable.id);

Hi Joost,

Yes, you're right, the above is superior to the NOT EXIST.  The NOT 
EXIST's Execution Plan shows it will perform a full table scan (Seq 
Scan) of [pimitemflagrelation].

I find NOT EXIST to nearly always be non-performant across all RDBMS's.

Too bad the LEFT OUTER JOIN doesn't work in the FROM for PG.

Cheers,

--
Pablo Sanchez - Blueoak Database Engineering, Inc
Ph:    819.459.1926         Blog:  http://pablo-blog.blueoakdb.com
iNum:  883.5100.0990.1054

_______________________________________________
KDE PIM users mailing list
Subscription management: https://mail.kde.org/mailman/listinfo/kdepim-users