Search Postgresql Archives

Re: A possible use case for: "INSERT .. ON CONFLICT DO SELECT [FOR ..]"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Nov 4, 2017 at 6:41 PM, Marc-Olaf Jaschke <moj@xxxxxxxxx> wrote:
Perhaps I misunderstand the discussion but would "INSERT .. ON CONFLICT DO SELECT [FOR ..]" not provide a solution for the following use case?

[ .. ]

That works. But it is a bit inconvenient to write the pseudo update clause.

Right.  This is exactly the use case for  ON CONFLICT DO SELECT.  The "no-op" UPDATE bloats the table unnecessary and just generally results in unnecessary overhead.


.m

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux