| From: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>, "Grzegorz =?utf-8?q?Ja=C5=9Bkiewicz?=" <gryzman(at)gmail(dot)com> |
| Subject: | Re: left join with smaller table or index on (XXX is not null) to avoid upsert |
| Date: | 2009-01-20 17:37:08 |
| Message-ID: | 200901201837.11136.dfontaine@hi-media.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
Le lundi 19 janvier 2009, Tom Lane a écrit :
> But having said that: 8.4 will provide a standard trigger that
> short-circuits vacuous updates, which you can apply to tables in which
> you think vacuous updates are likely. It's your responsibility to place
> the trigger so that it doesn't interfere with any other trigger
> processing you may have.
I'm preparing an 8.3 backport of it, which in fact is running just fine
already now. Would pgfoundry let me chekout the module I imported earlier
today the code and debian packaging would be on a public CVS already.
http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/backports/min_update/
If people want to see the code before pgfoundry allows me to put it in the CVS
overthere, here it is (slow server):
http://pgsql.tapoueh.org/min_update
Regards,
--
dim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dennis C | 2009-01-20 18:15:36 | Re: pg_restore: [archiver] entry ID -825110830 out of range -- perhaps a corrupt TOC |
| Previous Message | Adrian Klaver | 2009-01-20 16:28:38 | Re: import sql dump with psql - language creation throws error |