Re: Duplicate deletion optimizations

It was not query... Just sentence where some index values in one table
not exist in another...

So query could be with:
=E2=80=A2 WHERE (col1,col2,col2) NOT IN
=E2=80=A2 WHERE NOT EXISTS
=E2=80=A2 LEFT JOIN live USING (col1,col2,col2) WHERE live.id IS NULL

what ever whoever prefer more or what gives better results... But I
think it is more personal feelings which is better then real...

Sent from my Windows Phone
From: Jochen Erwied
Sent: 07/01/2012 15:18
To: Misa Simic
Cc: pgsql-performance@postgresql.org
Subject: Re: [PERFORM] Duplicate deletion optimizations
Saturday, January 7, 2012, 3:02:10 PM you wrote:

> =E2=80=A2 insert into live from temp where col1, col2 and col3 not exists=
 in
> live

'not exists' is something I'm trying to avoid, even if the optimizer is
able to handle it.

--=20
Jochen Erwied     |   home: jochen@erwied.eu     +49-208-38800-18, FAX: -19
Sauerbruchstr. 17 |   work: joe@mbs-software.de  +49-2151-7294-24, FAX: -50
D-45470 Muelheim  | mobile: jochen.erwied@vodafone.de       +49-173-5404164