- 30 11月, 2001 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 29 11月, 2001 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 22 11月, 2001 1 次提交
-
-
由 Tom Lane 提交于
-
- 21 11月, 2001 2 次提交
-
-
由 Thomas G. Lockhart 提交于
Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
-
由 Bruce Momjian 提交于
libpq.sgml I was trying (but gave up) to cross-reference back to the input escape table in the User's Guide, but could not get the documentation to compile with a cross-book xref (missing IDREF error). Can a cross-book xref be done? Joe Conway
-
- 19 11月, 2001 2 次提交
- 13 11月, 2001 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 01 11月, 2001 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 13 10月, 2001 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 13 9月, 2001 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 11 9月, 2001 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 09 9月, 2001 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 08 9月, 2001 1 次提交
-
-
由 Bruce Momjian 提交于
discussion on pgsql-hackers (especially the frightening memory dump in <12273.999562219@sss.pgh.pa.us>), we decided that it is best not to use identifiers from an untrusted source at all. Therefore, all claims of the suitability of PQescapeString() for identifiers have been removed. Florian Weimer
-
- 04 9月, 2001 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 28 8月, 2001 1 次提交
-
-
由 Peter Eisentraut 提交于
Client headers are no longer in a subdirectory, since they have been made namespace-clean. Internal libpq headers are in a private subdirectory. Server headers are in a private subdirectory. pg_config has a new option to point there.
-
- 11 8月, 2001 1 次提交
-
-
由 Tom Lane 提交于
our own code ...
-
- 10 8月, 2001 1 次提交
-
-
由 Bruce Momjian 提交于
appears to be duplicated (two identical <listitems> right after each other). Here is a quick patch to remove one instance of it. Magnus Hagander
-
- 31 7月, 2001 1 次提交
-
-
由 Tom Lane 提交于
anymore.
-
- 13 5月, 2001 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 01 5月, 2001 3 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
libpq and libpq++ reorganized.
-
- 22 3月, 2001 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 05 3月, 2001 1 次提交
-
-
由 Peter Eisentraut 提交于
Mikhail Terekhov <terekhov@emc.com>.
-
- 21 1月, 2001 1 次提交
-
-
由 Peter Eisentraut 提交于
syntax, type names, function names, etc.)
-
- 18 1月, 2001 1 次提交
-
-
由 Thomas G. Lockhart 提交于
-
- 14 1月, 2001 1 次提交
-
-
由 Peter Eisentraut 提交于
etc.
-
- 28 12月, 2000 1 次提交
-
-
由 Tom Lane 提交于
-
- 23 12月, 2000 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 22 12月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
Alfred Perlstein
-
- 01 12月, 2000 2 次提交
-
-
由 Tom Lane 提交于
I hope all the dust has settled out now ...
-
由 Peter Eisentraut 提交于
-
- 28 11月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 22 11月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 14 11月, 2000 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
leading slash to behave as a unix socket path.
-
- 13 11月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
hosting product, on both shared and dedicated machines. We currently offer Oracle and MySQL, and it would be a nice middle-ground. However, as shipped, PostgreSQL lacks the following features we need that MySQL has: 1. The ability to listen only on a particular IP address. Each hosting customer has their own IP address, on which all of their servers (http, ftp, real media, etc.) run. 2. The ability to place the Unix-domain socket in a mode 700 directory. This allows us to automatically create an empty database, with an empty DBA password, for new or upgrading customers without having to interactively set a DBA password and communicate it to (or from) the customer. This in turn cuts down our install and upgrade times. 3. The ability to connect to the Unix-domain socket from within a change-rooted environment. We run CGI programs chrooted to the user's home directory, which is another reason why we need to be able to specify where the Unix-domain socket is, instead of /tmp. 4. The ability to, if run as root, open a pid file in /var/run as root, and then setuid to the desired user. (mysqld -u can almost do this; I had to patch it, too). The patch below fixes problem 1-3. I plan to address #4, also, but haven't done so yet. These diffs are big enough that they should give the PG development team something to think about in the meantime :-) Also, I'm about to leave for 2 weeks' vacation, so I thought I'd get out what I have, which works (for the problems it tackles), now. With these changes, we can set up and run PostgreSQL with scripts the same way we can with apache or proftpd or mysql. In summary, this patch makes the following enhancements: 1. Adds an environment variable PGUNIXSOCKET, analogous to MYSQL_UNIX_PORT, and command line options -k --unix-socket to the relevant programs. 2. Adds a -h option to postmaster to set the hostname or IP address to listen on instead of the default INADDR_ANY. 3. Extends some library interfaces to support the above. 4. Fixes a few memory leaks in PQconnectdb(). The default behavior is unchanged from stock 7.0.2; if you don't use any of these new features, they don't change the operation. David J. MacKenzie
-