Re: [PATCHES] more fixes for making contrib null safe
On Fri, 28 Jan 2005, Kris Jurka wrote: This adds the strict function attribute to the places in contrib that crash on null inputs. Doesn't C need to be quoted? A few of those looked like this: LANGUAGE C STRICT but I thought it should be: LANGUAGE 'C' STRICT Is that right? Jon -- Jon Jensen End Point Corporation http://www.endpoint.com/ Software development with Interchange, Perl, PostgreSQL, Apache, Linux, ... ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [PATCHES] more fixes for making contrib null safe
On Fri, 28 Jan 2005, Kris Jurka wrote: Doesn't C need to be quoted? A few of those looked like this: LANGUAGE C STRICT This is perfectly legal: http://developer.postgresql.org/docs/postgres/sql-createfunction.html langname The name of the language that the function is implemented in. May be SQL, C, internal, or the name of a user-defined procedural language. For backward compatibility, the name may be enclosed by single quotes. Oh, ok. Good to know. Thanks, Jon -- Jon Jensen End Point Corporation http://www.endpoint.com/ Software development with Interchange, Perl, PostgreSQL, Apache, Linux, ... ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[PATCHES] Update for documentation on CVS
This is a little patch to correct the documentation on CVS. The URL for downloading CVS at cyclic.com site is long defunct, and I changed the text to not overtly recommend CVS 1.10, a now fairly old version. Jon -- Jon Jensen End Point Corporation http://www.endpoint.com/ Software development with Interchange, Perl, PostgreSQL, Apache, Linux, ...Index: sgml/cvs.sgml === RCS file: /projects/cvsroot/pgsql/doc/src/sgml/cvs.sgml,v retrieving revision 1.28 diff -u -c -r1.28 cvs.sgml *** sgml/cvs.sgml 27 Sep 2004 05:54:58 - 1.28 --- sgml/cvs.sgml 2 Dec 2004 00:46:51 - *** *** 52,61 para You will need a local copy of productnameCVS/productname (Concurrent Version Control System), which you can get from ! ulink url=http://www.cyclic.com/;http://www.cyclic.com//ulink or ! any GNU software archive site. ! We currently recommend version 1.10 (the most recent at the time ! of writing). Many systems have a recent version of applicationcvs/application installed by default. /para /step --- 52,61 para You will need a local copy of productnameCVS/productname (Concurrent Version Control System), which you can get from ! ulink url=http://www.cvshome.org/;http://www.cvshome.org//ulink ! (the official site with the latest version) or any GNU software ! archive site (often somewhat outdated). We recommend version 1.10 ! or newer. Many systems have a recent version of applicationcvs/application installed by default. /para /step *** *** 167,173 For more info consult the manual that comes with productnameCVS/productname, or see the online documentation at !ulink url=http://www.cyclic.com/;http://www.cyclic.com//ulink. /para /sect1 --- 167,173 For more info consult the manual that comes with productnameCVS/productname, or see the online documentation at !ulink url=http://www.cvshome.org/;http://www.cvshome.org//ulink. /para /sect1 ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[PATCHES] pg_hba.conf patch for hostnossl
Hello. When I sent in the sslmode patch I forgot to update the comments/examples in pg_hba.conf. This patch remedies that, adds a brief explanation of the connection types, and adds a missing period in the docs. JonIndex: doc/src/sgml/client-auth.sgml === RCS file: /projects/cvsroot/pgsql-server/doc/src/sgml/client-auth.sgml,v retrieving revision 1.57 diff -c -r1.57 client-auth.sgml *** doc/src/sgml/client-auth.sgml 5 Sep 2003 20:31:35 - 1.57 --- doc/src/sgml/client-auth.sgml 11 Sep 2003 00:20:48 - *** *** 102,108 para This record matches connection attempts using Unix-domain sockets. Without a record of this type, Unix-domain socket !connections are disallowed /para /listitem /varlistentry --- 102,108 para This record matches connection attempts using Unix-domain sockets. Without a record of this type, Unix-domain socket !connections are disallowed. /para /listitem /varlistentry Index: src/backend/libpq/pg_hba.conf.sample === RCS file: /projects/cvsroot/pgsql-server/src/backend/libpq/pg_hba.conf.sample,v retrieving revision 1.46 diff -c -r1.46 pg_hba.conf.sample *** src/backend/libpq/pg_hba.conf.sample7 Sep 2003 03:36:03 - 1.46 --- src/backend/libpq/pg_hba.conf.sample11 Sep 2003 00:20:48 - *** *** 7,21 # # This file controls: which hosts are allowed to connect, how clients # are authenticated, which PostgreSQL user names they can use, which ! # databases they can access. Records take one of five forms: # ! # localDATABASE USER METHOD [OPTION] ! # host DATABASE USER IP-ADDRESS IP-MASK METHOD [OPTION] ! # hostssl DATABASE USER IP-ADDRESS IP-MASK METHOD [OPTION] ! # host DATABASE USER IP-ADDRESS/CIDR-MASK METHOD [OPTION] ! # hostssl DATABASE USER IP-ADDRESS/CIDR-MASK METHOD [OPTION] # # (The uppercase quantities should be replaced by actual values.) # DATABASE can be all, sameuser, samegroup, a database name (or # a comma-separated list thereof), or a file name prefixed with @. # USER can be all, an actual user name or a group name prefixed with --- 7,26 # # This file controls: which hosts are allowed to connect, how clients # are authenticated, which PostgreSQL user names they can use, which ! # databases they can access. Records take one of seven forms: # ! # local DATABASE USER METHOD [OPTION] ! # host DATABASE USER IP-ADDRESS IP-MASK METHOD [OPTION] ! # hostsslDATABASE USER IP-ADDRESS IP-MASK METHOD [OPTION] ! # hostnossl DATABASE USER IP-ADDRESS IP-MASK METHOD [OPTION] ! # host DATABASE USER IP-ADDRESS/CIDR-MASK METHOD [OPTION] ! # hostsslDATABASE USER IP-ADDRESS/CIDR-MASK METHOD [OPTION] ! # hostnossl DATABASE USER IP-ADDRESS/CIDR-MASK METHOD [OPTION] # # (The uppercase quantities should be replaced by actual values.) + # The first field is the connection type: local is a Unix-domain socket, + # host is either a plain or SSL-encrypted TCP/IP socket, hostssl is an + # SSL-encrypted TCP/IP socket, and hostnossl is a plain TCP/IP socket. # DATABASE can be all, sameuser, samegroup, a database name (or # a comma-separated list thereof), or a file name prefixed with @. # USER can be all, an actual user name or a group name prefixed with ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings