2378 Commits (306798ded52cfd72e4fa7c0923c94de8b07bd739)

Author	SHA1	Message	Date
Peter Eisentraut	4284002d35	Markup examples as examples. Fix formatting of examples.	25 years ago
Peter Eisentraut	184c4afcd6	Some formatting changes, add CSS stylesheet. Include indexes in ... documentation tarball builds.	25 years ago
Tatsuo Ishii	113cf00edf	Add semicolon	25 years ago
Tatsuo Ishii	b4982f9b6d	Fix typo.	25 years ago
Tatsuo Ishii	f9d2749a03	Fix exmaple ... Tatsuo Ishii	25 years ago
Tatsuo Ishii	03df474440	Fix show message ... Tatsuo Ishii	25 years ago
Tatsuo Ishii	e38664aaa2	Add semicolon ... Tatsuo Ishii	25 years ago
Tatsuo Ishii	479cba8367	Example rules do not work. ... CREATE RULE bad_rule_combination_1 AS ON SELECT TO emp DO INSTEAD SELECT * FROM toyemp; CREATE RULE bad_rule_combination_2 AS ON SELECT TO toyemp DO INSTEAD SELECT * FROM emp; Tatsuo Ishii	25 years ago
Tatsuo Ishii	3f45796c7b	Add semicolon	25 years ago
Tatsuo Ishii	147c742aa2	Add semicolon ... Tatsuo Ishii	25 years ago
Bruce Momjian	4f0e6e3345	Update TODO list.	25 years ago
Bruce Momjian	5be2182e47	Update TODO list.	25 years ago
Bruce Momjian	2dcdd5fa53	Update TODO list.	25 years ago
Peter Eisentraut	76273a51a8	Update compatibility information.	25 years ago
Peter Eisentraut	861a0d7b5a	Update compatibility information.	25 years ago
Peter Eisentraut	a6496a2338	Update compatibility information.	25 years ago
Peter Eisentraut	351a0c1736	Replace ASCII-quotes with proper markup.	25 years ago
Peter Eisentraut	f93449eb34	'chown -R postgres /usr/local/pgsql' is wrong. Need to do some more typing.	25 years ago
Bruce Momjian	aaed778074	Attached patch is correction for 'doc/jdbc.sgml' of PostgreSQL 7.1.3. ... Correction content: * I revised a mistake of type (copy and paste). * I revised multiplicity of description. Ryouichi Matsuda	25 years ago
Bruce Momjian	0b8a76b24d	Followings are proposed fixes to jdbc.sgml(line numbers are for 7.1.3 ... doc). Hiroyuki Yatabe	25 years ago
Peter Eisentraut	dfdbf6898f	max_locks_per_transaction seems to be a more consistent name than ... max_locks_per_xact.	25 years ago
Bruce Momjian	33a82e7fd8	Here's some matching documentation, including some other ... undocumented items in TD. Should doc patches alse be sent to pgsql-patches, or do I have to subscribe to pgsql-docs? The archive link for pgsql-patches is broken, and I don't see any patches in spot checking the archive for pgsql-docs. -Brad McLean.	25 years ago
Tatsuo Ishii	3b99f74d95	Fix typo (add ;)	25 years ago
Tatsuo Ishii	2d12bc1ea1	Fix typo (add ;)	25 years ago
Tatsuo Ishii	7dc4a45ae7	Fix typo.	25 years ago
Tatsuo Ishii	95dc7785b5	Add single quote (example given here does not work)	25 years ago
Bruce Momjian	14fa192d46	Update TODO list.	25 years ago
Tatsuo Ishii	d7f3cbc288	Fix regression test in the case of building as root.	25 years ago
Peter Eisentraut	a457d33516	Markup and spell-check run over Programmer's Guide (rather incomplete still).	25 years ago
Bruce Momjian	0682c26ed5	Update TODO list.	25 years ago
Tatsuo Ishii	531126c854	Short version of install procedure fails due to lacking chown.	25 years ago
Tatsuo Ishii	35d3c85ac0	The usage of kill is incorrect (lacks "data"). Anyway we should use ... pg_ctl instead.	25 years ago
Tatsuo Ishii	acb66fc5bf	Fix typo. split does not produce ".".	25 years ago
Tatsuo Ishii	0e76f1bb1a	Fix typo.	25 years ago
Tatsuo Ishii	f8f0ff6b57	Example program lacks RETURN	25 years ago
Tatsuo Ishii	82b889a044	Fix typo.	25 years ago
Tatsuo Ishii	0d04ffeb0d	Fix typo.	25 years ago
Tatsuo Ishii	16a7ec386e	Fix initlocation messages	25 years ago
Bruce Momjian	bb35e499ea	Remove mention of INV_ARCHIVE.	25 years ago
Tatsuo Ishii	ea41e77c22	fix typo.	25 years ago
Tatsuo Ishii	aa398e5034	Add missing ';'	25 years ago
Bruce Momjian	98d04116d3	Update TODO list.	25 years ago
Bruce Momjian	df7664c166	Update TODO list.	25 years ago
Peter Eisentraut	d07454f559	Markup additions and spell check. (covers Admin Guide)	25 years ago
Peter Eisentraut	84956e71a3	Markup additions and spell check. (covers User's Guide)	25 years ago
Peter Eisentraut	1a63ef056e	fix markup	25 years ago
Peter Eisentraut	c0d4d5473a	Make the world somewhat safe for (not from) DELETE FROM pg_shadow; ... Assign the fixed user id 1 to the user created by initdb. A stand-alone backend will always set the user id to 1. (Consequently, the name of that user is no longer important.) In stand-alone mode, the user id 1 will have implicit superuser status, to allow repairs even if there are no users defined. Print a warning message when starting in stand-alone mode when no users are defined. Disallow dropping the current user and session user. Granting/revoking superuser status also grants/revokes usecatupd. (Previously, it would never grant it back. This could lead to "deadlocks".) CREATE USER and CREATE GROUP will start allocating user ids at 100 (unless explicitly specified), to prevent accidental creation of a superuser (plus some room for future extensions).	25 years ago
Bruce Momjian	20dd23c47a	Update TODO list.	25 years ago
Bruce Momjian	1834987fb6	I've attached the fixed version of the patch below. After the ... 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	25 years ago
Bruce Momjian	bd9b32803b	Here is my much-promised patch to let people add UNIQUE constraints after ... table creation time. Big deal you say - but this patch is the basis of the next thing which is adding PRIMARY KEYs after table creation time. (Which is currently impossible without twiddling catalogs) Rundown ------- * I have made the makeObjectName function of analyze.c non-static, and exported it in analyze.h * I have included analyze.h and defrem.h into command.c, to support makingObjectNames and creating indices * I removed the 'case CONSTR_PRIMARY' clause so that it properly fails and says you can't add primary keys, rather than just doing nothing and reporting nothing!!! * I have modified the docs. Algorithm --------- * If name specified is null, search for a new valid constraint name. I'm not sure if I should "lock" my generated name somehow tho - should I open the relation before doing this step? * Open relation in access exclusive mode * Check that the constraint does not already exist * Define the new index * Warn if they're doubling up on an existing index Christopher Kings-Lynne	25 years ago