Re: MERGE vs REPLACE - Mailing list pgsql-hackers

From Jaime Casanova
Subject Re: MERGE vs REPLACE
Date
Msg-id c2d9e70e0511160833l24dc90fdu4e99b2bc669c8277@mail.gmail.com
Whole thread Raw
In response to Re: MERGE vs REPLACE  (Rick Gigger <rick@alpinenetworking.com>)
List pgsql-hackers
> You could also just add something to the merge syntax like ALLOW
> TABLE LOCK or something.  The idea is just that the user can
> explicitly allow the table lock and thus the more complicated merge.
>

The problem here is that many people will see that option and think
it's safe to do it... i mean, many people will shoot themselves in the
foot and the culprit will be PostgreSQL because he let a ready to
shoot gun in a visible place when are kids around

--
regards,
Jaime Casanova
(DBA: DataBase Aniquilator ;)


pgsql-hackers by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: OS X 7.4 failure
Next
From: Grzegorz Jaskiewicz
Date:
Subject: Re: question about count(b) where b is a custom type