Re: left join with smaller table or index on (XXX is not null) to avoid upsert

From: Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>
To: Alex Hunsaker <badalex(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: left join with smaller table or index on (XXX is not null) to avoid upsert
Date: 2009-01-20 15:40:52
Message-ID: 2f4958ff0901200740o623ba9c3pc8f42b108f951aaf@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

the only difference here is, that the trigger will memcmp (compare)
all data. Say, if we have two columns, int and bytea, and just want to
compare fist one - it will use a lot of cpu in vain.
I have to say, it is a shame sometimes - that trigger isn't aware of
what fields we do update exactly

In response to

Browse pgsql-general by date

  From Date Subject
Next Message David Fetter 2009-01-20 15:44:06 Re: Database schema & data synchronizer software for PostgreSQL?
Previous Message Adrian Klaver 2009-01-20 15:18:08 Re: import sql dump with psql - language creation throws error