From: | Misa Simic <misa(dot)simic(at)gmail(dot)com> |
---|---|
To: | Jochen Erwied <jochen(at)pgsql-performance(dot)erwied(dot)eu> |
Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Duplicate deletion optimizations |
Date: | 2012-01-07 20:16:13 |
Message-ID: | -1818149885061307584@unknownmsgid |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
It was not query... Just sentence where some index values in one table
not exist in another...
So query could be with:
• WHERE (col1,col2,col2) NOT IN
• WHERE NOT EXISTS
• 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(at)postgresql(dot)org
Subject: Re: [PERFORM] Duplicate deletion optimizations
Saturday, January 7, 2012, 3:02:10 PM you wrote:
> • 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.
--
Jochen Erwied | home: jochen(at)erwied(dot)eu +49-208-38800-18, FAX: -19
Sauerbruchstr. 17 | work: joe(at)mbs-software(dot)de +49-2151-7294-24, FAX: -50
D-45470 Muelheim | mobile: jochen(dot)erwied(at)vodafone(dot)de +49-173-5404164
From | Date | Subject | |
---|---|---|---|
Next Message | Marc Eberhard | 2012-01-07 22:54:20 | Re: Duplicate deletion optimizations |
Previous Message | Jeff Janes | 2012-01-07 18:54:51 | Re: Duplicate deletion optimizations |