| From: | Anssi Kääriäinen <anssi(dot)kaariainen(at)thl(dot)fi> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Kevin Grittner <kgrittn(at)ymail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: INSERT ... ON CONFLICT {UPDATE | IGNORE} |
| Date: | 2014-12-08 10:43:54 |
| Message-ID: | 1418035434.22478.119.camel@TTY32 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 2014-12-05 at 10:00 -0800, Josh Berkus wrote:
> I thought the point of INSERT ... ON CONFLICT update was so that you
> didn't have to care if it was a new row or not?
>
> If you do care, it seems like it makes more sense to do your own INSERTs
> and UPDATEs, as Django currently does.
Django tries to update the object if it already exists in the database.
If it doesn't, then Django does an insert. This is suboptimal from
concurrency standpoint, and does two round trips to the database instead
of just one.
For Django, both insert and update are OK when saving an object to the
database, but Django needs to know which one was done.
I too agree that this doesn't need to be handled in the first version of
the patch.
- Anssi
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Etsuro Fujita | 2014-12-08 12:10:37 | Re: inherit support for foreign tables |
| Previous Message | Craig Ringer | 2014-12-08 10:38:43 | Re: [Windows,PATCH] Use faster, higher precision timer API |