[HACKERS] Minor patch for the uuid-ossp extension

2013-11-22 Thread roadrunner6

When trying to add the extension with \i it writes an error message:
Use CREATE EXTENSION uuid-ossp to load this file.

Unfortunatly this does not work for extensions with dashes. Must CREATE 
EXTENSION uuid-ossp. Proposed patch is attached.


Regards
Mario

diff -Nurb contrib.orig/uuid-ossp/uuid-ossp--1.0.sql 
contrib/uuid-ossp/uuid-ossp--1.0.sql
--- contrib.orig/uuid-ossp/uuid-ossp--1.0.sql   2013-11-22 13:48:21.588674030 
+0100
+++ contrib/uuid-ossp/uuid-ossp--1.0.sql2013-11-22 13:52:13.232387782 
+0100
@@ -1,7 +1,7 @@
 /* contrib/uuid-ossp/uuid-ossp--1.0.sql */

 -- complain if script is sourced in psql, rather than via CREATE EXTENSION
-\echo Use CREATE EXTENSION uuid-ossp to load this file. \quit
+\echo Use CREATE EXTENSION uuid-ossp to load this file. \quit

 CREATE FUNCTION uuid_nil()
 RETURNS uuid
diff -Nurb contrib.orig/uuid-ossp/uuid-ossp--unpackaged--1.0.sql 
contrib/uuid-ossp/uuid-ossp--unpackaged--1.0.sql
--- contrib.orig/uuid-ossp/uuid-ossp--unpackaged--1.0.sql   2013-11-22 
13:44:04.589862871 +0100
+++ contrib/uuid-ossp/uuid-ossp--unpackaged--1.0.sql2013-11-22 
13:52:19.480164238 +0100
@@ -1,7 +1,7 @@
 /* contrib/uuid-ossp/uuid-ossp--unpackaged--1.0.sql */

 -- complain if script is sourced in psql, rather than via CREATE EXTENSION
-\echo Use CREATE EXTENSION uuid-ossp to load this file. \quit
+\echo Use CREATE EXTENSION uuid-ossp to load this file. \quit

 ALTER EXTENSION uuid-ossp ADD function uuid_nil();
 ALTER EXTENSION uuid-ossp ADD function uuid_ns_dns();
-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers


Re: [HACKERS] Extra security measures for next week's releases

2013-04-03 Thread roadrunner6

Am 28.03.2013 18:03, schrieb Tom Lane:

The core committee has decided that one of the security issues due to be
fixed next week is sufficiently bad that we need to take extra measures
to prevent it from becoming public before packages containing the fix
are available.  (This is a scenario we've discussed before, but never
had to actually implement.)



8.3 has reached EOL in February 2013, I guess there will be no fix for 
8.3, right?





--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers