713 Commits (0cb6bc70cec12d4fbcb68673bd73453061de89f2)

Author	SHA1	Message	Date
Bruce Momjian	41d4548b0f	Freebsd update for sgml, from Alfred Perlstein	26 years ago
Bruce Momjian	10d7287ab9	Libpq non-blocking mode, from Alfred Perlstein	26 years ago
Peter Eisentraut	28125ed5e0	Updated user interfaces on initdb, initlocation, pg_dump, ipcclean to a GNU-compliant'ish state. ... Made ipcclean work on Linux.	26 years ago
Bruce Momjian	6759f4388f	Update TODO list.	26 years ago
Peter Eisentraut	759fba4873	Included all yacc and lex files into the distribution.	26 years ago
Bruce Momjian	1b6b4d40ed	Update TODO list.	26 years ago
Bruce Momjian	fae5d81c68	Update TODO list.	26 years ago
Bruce Momjian	255e07e829	Update TODO list.	26 years ago
Bruce Momjian	3a2e08618c	Update TODO list.	26 years ago
Bruce Momjian	0f4a586821	Update TODO list.	26 years ago
Peter Eisentraut	2a1bfbce24	- Allow array on int8 ... - Prevent permissions on indexes - Instituted --enable-multibyte option and tweaked the MB build process where necessary - initdb prompts for superuser password	26 years ago
Peter Eisentraut	7c9390caa1	Fixed psql variables vs array syntax, as well as minor psql enhancements	26 years ago
Peter Eisentraut	4ceb2d0cb6	* User management commands no longer user pg_exec_query_dest -> more robust ... * Let unprivileged users change their own passwords. * The password is now an Sconst in the parser, which better reflects its text datatype and also forces users to quote them. * If your password is NULL you won't be written to the password file, meaning you can't connect until you have a password set up (if you use password authentication). * When you drop a user that owns a database you get an error. The database is not gone.	26 years ago
Tom Lane	2af360ed1c	Clean up some problems in new asynchronous-connection logic ... in libpq --- mostly, poor response to error conditions. You now actually get to see the postmaster's 'The Data Base System is starting up' message, which you didn't before. I suspect the SSL code is still broken though.	26 years ago
Bruce Momjian	bb7e85fb85	Update TODO list.	26 years ago
Bruce Momjian	e419b48217	Update TODO list.	26 years ago
Bruce Momjian	3af969d4a0	Update TODO list.	26 years ago
Bruce Momjian	af53b624f0	Update TODO list.	26 years ago
Bruce Momjian	326a69deeb	Update TODO list.	26 years ago
Bruce Momjian	e589b9e821	Update TODO list.	26 years ago
Bruce Momjian	7c25123df4	Update TODO list.	26 years ago
Bruce Momjian	c6035cd173	Update TODO list.	26 years ago
Peter Eisentraut	f6689a328f	Fixed a few "fixes" and bugs. Adjusted messages and options to GNU suggestions.	26 years ago
Bruce Momjian	142ce7939d	Update TODO list.	26 years ago
Tom Lane	ac295f43f5	Update struct Trigger definition.	26 years ago
Tom Lane	ac401e06c5	Change oid8/int28 -> oidvector/int2vector.	26 years ago
Bruce Momjian	752314eb26	Update TODO list.	26 years ago
Bruce Momjian	8cc9d8454b	Update TODO list.	26 years ago
Tom Lane	b86ca72f39	Update platform-specific-expected-file support so that platforms can be ... specified by regular-expression patterns. Add some more files.	26 years ago
Bruce Momjian	aa48a22a82	The psql online help for ALTER TABLE (\h alter table) is corrupt. I ... traced this back to what I believe is an error in the sgml file used to generate this comment, found in pgsql/doc/src/sgml/ref/alter_table.sgml. Stephen Birch	26 years ago
Bruce Momjian	b16bd18546	Clearify DECLARE syntax by saying cursorname, not just cursor.	26 years ago
Bruce Momjian	649ffe1616	Improve subquery error message, now says "More than one tuple returned ... by subselect used as expression."	26 years ago
Bruce Momjian	e1b212ff3b	Move ipc patch into README.NT.	26 years ago
Bruce Momjian	ad322de0ae	Update developers faq.	26 years ago
Bruce Momjian	a0fa26bef6	Update developers faq in main tree.	26 years ago
Bruce Momjian	1c2257648a	> > It would be nice for new users; I think it would make it easier ...	26 years ago
Thomas G. Lockhart	97710d9f5a	Fix typo in tag.	26 years ago
Bruce Momjian	83bad7c063	This is my -- hopefully sufficiently portable -- attempt at cleaning out ... initdb. No more obscure dependencies on environment variables or paths. It now finds the templates and the right postgres itself (with cmd line options as fallback). It also no longer depends on $USER (su safe), and doesn't advertise that --username allows you to install the db as a different user, since that doesn't work anyway. Also, recovery and cleanup on all errors. Consistent options, clearer documentation. Please take a look at this and adopt it if you feel it's safe enough. I have simulated all the stupid circumstances I could think of, but you never know with shell scripts. Oh yeah, you can give the postgres user a default password now. -- Peter Eisentraut Sernanders väg 10:115	26 years ago
Bruce Momjian	4cb1fb6f59	Update for QNX.	26 years ago
Bruce Momjian	549a8ba59a	> From what I gather, this should be a little cleaner because the ... triggered > function now returns the right datatype. Oops, I got crossed up with Jan's improvements. Ignore this. -- Peter Eisentraut Sernanders väg 10:115 peter_e@gmx.net 75262 Uppsala	26 years ago
Bruce Momjian	bcaabc5698	Depending on my interpreting (and programming) skills, this might solve ... anywhere from zero to two TODO items. * Allow flag to control COPY input/output of NULLs I got this: COPY table .... [ WITH NULL AS 'string' ] which does what you'd expect. The default is \N, otherwise you can use empty strings, etc. On Copy In this acts like a filter: every data item that looks like 'string' becomes a NULL. Pretty straightforward. This also seems to be related to * Make postgres user have a password by default If I recall this discussion correctly, the problem was actually that the default password for the postgres (or any) user is in fact "\N", because of the way copy is used. With this change, the file pg_pwd is copied out with nulls as empty strings, so if someone doesn't have a password, the password is just '', which one would expect from a new account. I don't think anyone really wants a hard-coded default password. Peter Eisentraut Sernanders väg 10:115	26 years ago
Tom Lane	ff6fe1502d	Update documentation to reflect availability of aggregate(DISTINCT). ... Try to provide a more lucid discussion in 'Using Aggregate Functions' tutorial section.	26 years ago
Bruce Momjian	cb00b7faa5	I'm in TODO mood today ... ... * Document/trigger/rule so changes to pg_shadow recreate pg_pwd I did it with a trigger and it seems to work like a charm. The function that already updates the file for create and alter user has been made a built-in "SQL" function and a trigger is created at initdb time. Comments around the pg_pwd updating function seem to be worried about this routine being called concurrently, but I really don't see a reason to worry about this. Verify for yourself. I guess we never had a system trigger before, so treat this with care, and feel free to adjust the nomenclature as well. -- Peter Eisentraut Sernanders väg 10:115	26 years ago
Bruce Momjian	11023eb1f5	Meanwhile, database names with single quotes in names don't work very well ... at all, and because of shell quoting rules this can't be fixed, so I put in error messages to that end. Also, calling create or drop database in a transaction block is not so good either, because the file system mysteriously refuses to roll back rm calls on transaction aborts. :) So I put in checks to see if a transaction is in progress and signal an error. Also I put the whole call in a transaction of its own to be able to roll back changes to pg_database in case the file system operations fail. The alternative location issues I posted recently were untouched, awaiting the outcome of that discussion. Other than that, this should be much more fool-proof now. The docs I cleaned up as well. Peter Eisentraut Sernanders väg 10:115	26 years ago
Bruce Momjian	e6ac08c398	Update TODO list.	26 years ago
Bruce Momjian	cb0032cdcf	Update for QNX from Kardos, Dr. Andrea	26 years ago
Bruce Momjian	a0aab48fcd	Okay, that should put us back in sync. These two patches (src & doc) are ... 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	26 years ago
Thomas G. Lockhart	1d8ce77233	Update entries with recent results for Alpha and ARM processors. ... Remove references to Ultrix; haven't heard from it for a *long* time :(	26 years ago
Thomas G. Lockhart	b7f6168516	Fix markup (a couple of missing tags) and renormalize.	26 years ago
Thomas G. Lockhart	b6332952b7	Remove references to PostgreSQL as "public-domain" since that has a ... specific meaning wrt copyright (or lack thereof).	26 years ago