| From: | Dev Kumkar <devdas(dot)kumkar(at)gmail(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Daniel Farina <daniel(at)heroku(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: "on existing update" construct |
| Date: | 2013-05-16 00:20:43 |
| Message-ID: | CALSLE1PCS2cNpGEYRTDRFrCu1uU1nF29MwQ4gUv1PR4wsAUEZQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Please do not top-post on the PostgreSQL lists. See <
http://idallen.com/topposting.html>
> Also, note that pgsql-hackers is entirely the wrong list for this sort of
question. You should have been asking on pgsql-general.
Apologies for top-post!
Well I thought pgsql-hackers will suggest some new solution was just going
by the description of mailing-list. Its worth looking into
http://stackoverflow.com/questions/1109061/insert-on-duplicate-update-postgresql
Let me know and I will post this question on pgsql-general.
> It's been on the TODO list forever. It's harder to implement well than
> you would think.
Yes, I think it be nice to see this in one of the upcoming releases.
Thanks!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-05-16 00:24:37 | Re: Heap truncation without AccessExclusiveLock (9.4) |
| Previous Message | Robert Haas | 2013-05-16 00:04:16 | Re: Heap truncation without AccessExclusiveLock (9.4) |