| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: MERGE Specification |
| Date: | 2008-04-22 02:27:12 |
| Message-ID: | 87ve2atyin.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
> Unrelated to rule processing, you did read the bit about MERGE and race
> conditions? ISTM that MERGE as it stands isn't very useful for anything
> other than large data loads since its going to cause problems if used
> concurrently.
If there are race conditions what advantage does it offer over writing plpgsql
or client code to do it?
I thought the whole advantage of having a built-in command is that it could do
the kind of locking our unique constraints do to avoid race conditions.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zdenek Kotala | 2008-04-22 05:58:03 | Re: Can't start psql |
| Previous Message | 王佳伟 | 2008-04-22 02:23:22 | Can't start psql |