- 29 May, 2005 1 commit
-
-
Bruce Momjian authored
-
- 29 Nov, 2003 1 commit
-
-
PostgreSQL Daemon authored
$Header: -> $PostgreSQL Changes ...
-
- 12 Sep, 2003 2 commits
- 09 Sep, 2003 1 commit
-
-
Tom Lane authored
discussion. (Still have some work to do editing the remainder.)
-
- 31 Aug, 2003 1 commit
-
-
Peter Eisentraut authored
-
- 17 Aug, 2003 1 commit
-
-
Bruce Momjian authored
spelling mistake in the PREPARE ref page (2) Makes some English more consistent, in the ref pages for some of the client apps (3) Adds a link to the libpq docs in the vacuumdb ref page. Neil Conway
-
- 18 Jun, 2003 1 commit
-
-
Peter Eisentraut authored
-
- 24 Mar, 2003 1 commit
-
-
Peter Eisentraut authored
-
- 20 Mar, 2003 1 commit
-
-
Bruce Momjian authored
be simplified (I'd thought that it can even be removed). This patch does that. Alvaro Herrera
-
- 19 Feb, 2003 1 commit
-
-
Bruce Momjian authored
- more work from the SGML police - some grammar improvements: rewriting a paragraph or two, replacing contractions where (IMHO) appropriate - fix missing utility commands in lock mode docs - improve CLUSTER, REINDEX, SET SESSION AUTHORIZATION ref pages Neil Conway
-
- 13 Feb, 2003 1 commit
-
-
Bruce Momjian authored
makes a few editorial changes to the documentation. Neil Conway
-
- 11 Oct, 2002 1 commit
-
-
Peter Eisentraut authored
-
- 21 Sep, 2002 1 commit
-
-
Peter Eisentraut authored
-
- 05 Sep, 2002 1 commit
-
-
Bruce Momjian authored
Cleanup up memory allocation for $HOME in related psql places. Update mention of $HOME/.pgpass in the docs; add mention in pg_dumpall.
-
- 03 Sep, 2002 1 commit
-
-
Tom Lane authored
-
- 27 Aug, 2002 1 commit
-
-
Bruce Momjian authored
bit on the indexes. I also attach clusterdb and clusterdb.sgml; both of them are blatant rips of vacuumdb and vacuumdb.sgml, but get the job done. Please review them, as I'm probably making a lot of mistakes with SGML and I can't compile it here. vacuumdb itself is not very comfortable to use when the databases have passwords, because it has to connect once for each table (I can probably make it connect only once for each database; should I?). Because of this I added a mention of PGPASSWORDFILE in the documentation, but I don't know if that is the correct place for that. Alvaro Herrera
-
- 10 Aug, 2002 1 commit
-
-
Peter Eisentraut authored
and database. In particular, make script wrappers understand the PGDATABASE environment variable.
-
- 28 Jul, 2002 1 commit
-
-
Peter Eisentraut authored
Add information about environment variables.
-
- 18 Feb, 2002 1 commit
-
-
Bruce Momjian authored
Properly handles default values.
-
- 08 Dec, 2001 1 commit
-
-
Thomas G. Lockhart authored
between Postgres and PostgreSQL.
-
- 28 Nov, 2001 1 commit
-
-
Peter Eisentraut authored
-
- 03 Sep, 2001 1 commit
-
-
Peter Eisentraut authored
-
- 10 Jul, 2001 1 commit
-
-
Tom Lane authored
USER and ALTER USER to appear in any order, not only the fixed order they used to be required to appear in. Also, some changes from Tom Lane to create a FULL option for VACUUM; it doesn't do anything yet, but I needed to change many of the same files to make that happen, so now seemed like a good time.
-
- 17 Mar, 2001 1 commit
-
-
Peter Eisentraut authored
-
- 25 Dec, 2000 1 commit
-
-
Peter Eisentraut authored
-
- 22 Nov, 2000 1 commit
-
-
Bruce Momjian authored
-
- 13 Nov, 2000 3 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
leading slash to behave as a unix socket path.
-
Bruce Momjian authored
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
-
- 11 Nov, 2000 1 commit
-
-
Peter Eisentraut authored
-
- 02 May, 2000 1 commit
-
-
Thomas G. Lockhart authored
-
- 27 Mar, 2000 1 commit
-
-
Thomas G. Lockhart authored
Use "generic functions" for math and other routines. Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
-
- 18 Dec, 1999 1 commit
-
-
Bruce Momjian authored
> > It would be nice for new users; I think it would make it easier > > for them to actually set out and do it. Many new users are > > of the not-so-knowledgable variety, and shell scripting isn't > > something they want to undertake. > > Can someone modify the vacuumdb shell script to do that? i tried it... it seems to work neko@kredit.sth.sz
-
- 07 Dec, 1999 1 commit
-
-
Bruce Momjian authored
against the sources from one hour ago and contain all the portable and up to date stuff. A few other CVS "householding" things you might want to take care of: * Remove the src/bin/cleardbdir directory * Remove the file src/bin/psql/sql_help.h from the repository, as it is a derived file and is build by the release_prep. Peter Eisentraut
-
- 22 Jul, 1999 1 commit
-
-
Thomas G. Lockhart authored
ecpg reference page still needs formatting.
-
- 14 Jul, 1999 1 commit
-
-
Thomas G. Lockhart authored
Add some internal cross references to select.sgml.
-
- 26 May, 1999 1 commit
-
-
Thomas G. Lockhart authored
Normalize markup for vacuumdb; content is the same.
-
- 29 Dec, 1998 1 commit
-
-
Thomas G. Lockhart authored
of Norm's Modular Style Sheets and jade/docbook. From Vince Vielhaber <vev@michvhf.com>.
-
- 14 Nov, 1998 1 commit
-
-
Thomas G. Lockhart authored
-