postgresql/contrib/pgrowlocks
Tom Lane 5484c0a980 Minor fixes in contrib installation scripts.
Extension scripts should never use CREATE OR REPLACE for initial object
creation.  If there is a collision with a pre-existing (probably
user-created) object, we want extension installation to fail, not silently
overwrite the user's object.  Bloom and sslinfo both violated this precept.

Also fix a number of scripts that had no standard header (the file name
comment and the \echo...\quit guard).  Probably the \echo...\quit hack
is less important now than it was in 9.1 days, but that doesn't mean
that individual extensions get to choose whether to use it or not.

And fix a couple of evident copy-and-pasteos in file name comments.

No need for back-patch: the REPLACE bugs are both new in 9.6, and the
rest of this is pretty much cosmetic.

Andreas Karlsson and Tom Lane
2016-06-14 10:47:06 -04:00
..
Makefile Update pgrowlocks extension for parallel query. 2016-06-09 17:35:53 -04:00
pgrowlocks--1.0--1.1.sql Fix typo in update scripts for some contrib modules. 2013-07-19 04:13:01 +09:00
pgrowlocks--1.1--1.2.sql Update pgrowlocks extension for parallel query. 2016-06-09 17:35:53 -04:00
pgrowlocks--1.2.sql Minor fixes in contrib installation scripts. 2016-06-14 10:47:06 -04:00
pgrowlocks--unpackaged--1.0.sql Fix typos in some error messages thrown by extension scripts when fed to psql. 2014-08-25 18:30:37 +02:00
pgrowlocks.c Optimize locking a tuple already locked by another subxact 2015-04-10 13:47:15 -03:00
pgrowlocks.control Update pgrowlocks extension for parallel query. 2016-06-09 17:35:53 -04:00