3951 Commits (d51df918970bcf42f915a3882bfdee5972aa9bad)

Author	SHA1	Message	Date
Tom Lane	adb1a6e95b	Improve EXPLAIN ANALYZE to show the time spent in each trigger when ... executing a statement that fires triggers. Formerly this time was included in "Total runtime" but not otherwise accounted for. As a side benefit, we avoid re-opening relations when firing non-deferred AFTER triggers, because the trigger code can re-use the main executor's ResultRelInfo data structure.	21 years ago
Tom Lane	6d3f74d801	Update and copy-edit description of privileges.	21 years ago
Tom Lane	6e26c00297	Fix to_date to behave reasonably when CC and YY fields are both used. ... Karel Zak	21 years ago
Bruce Momjian	87a4f9b6a3	Print URL in printed output..	21 years ago
Bruce Momjian	07ebb9fba9	Add URL of how to report bugs: ... http://www.chiark.greenend.org.uk/~sgtatham/bugs.html	21 years ago
Bruce Momjian	b1f57d88f5	Change Win32 O_SYNC method to O_DSYNC because that is what the method ... currently does. This is now the default Win32 wal sync method because we perfer o_datasync to fsync. Also, change Win32 fsync to a new wal sync method called fsync_writethrough because that is the behavior of _commit, which is what is used for fsync on Win32. Backpatch to 8.0.X.	21 years ago
Neil Conway	50ce8ab9fc	Revert changes to CREATE TRIGGER and ALTER TABLE ADD FOREIGN KEY locking, ... per request from Tom.	21 years ago
Tom Lane	87ba04eeaf	Add note about risks involved in replaying CREATE TABLESPACE commands ... from WAL. A couple other grammatical improvements too.	21 years ago
Neil Conway	f30c76ce8d	Adjust CREATE TRIGGER and ALTER TABLE ... ADD FOREIGN KEY to acquire ... ExclusiveLock rather than AccessExclusiveLock. This will allow concurrent SELECT queries to proceed on the table. Per discussion with Andrew at SuperNews.	21 years ago
Tom Lane	ee4ddac137	Convert index-related tuple handling routines from char 'n'/' ' to bool ... convention for isnull flags. Also, remove the useless InsertIndexResult return struct from index AM aminsert calls --- there is no reason for the caller to know where in the index the tuple was inserted, and we were wasting a palloc cycle per insert to deliver this uninteresting value (plus nontrivial complexity in some AMs). I forced initdb because of the change in the signature of the aminsert routines, even though nothing really looks at those pg_proc entries...	21 years ago
Tom Lane	91728fa26c	Add temp_buffers GUC variable to allow users to determine the size ... of the local buffer arena for temporary table access.	21 years ago
Bruce Momjian	5955ebe334	Add link to INSERT in docs. ... Robert Treat	21 years ago
Bruce Momjian	28d150d8e9	Update file system snapshot docs.	21 years ago
Bruce Momjian	118bf5bc22	Mention tablespaces as a problem for using file system snapshots.	21 years ago
Bruce Momjian	ca2d08579e	Document use of rsync for file system backups. ... Tino Wildenhain	21 years ago
Neil Conway	957f51ea6b	Add a reference to the documentation on alternate index operator classes in ... the locale docs. Patch from Chris KL, editorialization by Neil Conway.	21 years ago
Tom Lane	f97aebd162	Revise TupleTableSlot code to avoid unnecessary construction and disassembly ... of tuples when passing data up through multiple plan nodes. A slot can now hold either a normal "physical" HeapTuple, or a "virtual" tuple consisting of Datum/isnull arrays. Upper plan levels can usually just copy the Datum arrays, avoiding heap_formtuple() and possible subsequent nocachegetattr() calls to extract the data again. This work extends Atsushi Ogawa's earlier patch, which provided the key idea of adding Datum arrays to TupleTableSlots. (I believe however that something like this was foreseen way back in Berkeley days --- see the old comment on ExecProject.) A test case involving many levels of join of fairly wide tables (about 80 columns altogether) showed about 3x overall speedup, though simple queries will probably not be helped very much. I have also duplicated some code in heaptuple.c in order to provide versions of heap_formtuple and friends that use "bool" arrays to indicate null attributes, instead of the old convention of "char" arrays containing either 'n' or ' '. This provides a better match to the convention used by ExecEvalExpr. While I have not made a concerted effort to get rid of uses of the old routines, I think they should be deprecated and eventually removed.	21 years ago
Bruce Momjian	86ad33cd48	Update to 8.0.1.	21 years ago
Bruce Momjian	17c8276d24	Clean up win1252 documentation. Mention how we determine the number of ... bytes/character for each encoding.	21 years ago
Bruce Momjian	e7fb9f18bf	Add support for Win1252 encoding. ... Roland Volkmann	21 years ago
Neil Conway	9abced035d	Fix mistakes in SGML markup. From David Fetter.	21 years ago
Tom Lane	251d3f75d0	Note that the -F and -R command line options only affect unaligned ... output mode. This was already stated in other places in the psql reference page, but not here.	21 years ago
Bruce Momjian	d1022ce3a1	Document client-only encodings.	21 years ago
Bruce Momjian	4973296035	Fix typo on URL.	21 years ago
Bruce Momjian	a03bb609b3	Finalize character set documentation changes.	21 years ago
Neil Conway	c069655441	Allow ALTER FUNCTION to change a function's strictness, volatility, and ... whether or not it is a security definer. Changing a function's strictness is required by SQL2003, and the other capabilities make sense. Also, allow an optional RESTRICT noise word to be specified, for SQL conformance. Some trivial regression tests added and the documentation has been updated.	21 years ago
Bruce Momjian	cbc100af66	Increment all major version numbers in 8.0.X to force recompile of ... client aplications so 7.4.X releases can be installed on the same machine as 8.0.X.	21 years ago
Bruce Momjian	8264cbcb50	Remove CENTER tag.	21 years ago
Neil Conway	ff02d0a052	Make default_with_oids default to false -- user-created tables will now ... no longer include OIDs, unless WITH OIDS is specified or the default_with_oids configuration parameter is enabled. Update the docs accordingly.	21 years ago
Bruce Momjian	0edc2f14e0	More ordering adjustments.	21 years ago
Bruce Momjian	c151e6374c	Fix markup.	21 years ago
Bruce Momjian	119807e397	More markup changes.	21 years ago
Bruce Momjian	1c0aeec65b	More cleanups.	21 years ago
Bruce Momjian	cbe4b4163e	More improvements.	21 years ago
Bruce Momjian	a717ab6fa6	More additions to the table.	21 years ago
Bruce Momjian	1fa8445233	Keep changing the markup until I like it. :-)	21 years ago
Bruce Momjian	382f24b187	More table markup improvements.	21 years ago
Bruce Momjian	7b7abb7ccb	More table markup fixes.	21 years ago
Bruce Momjian	6109a1ce18	Rework "aliases" column for encodings.	21 years ago
Bruce Momjian	074ba31e41	Fix markup typo.	21 years ago
Bruce Momjian	f949baf9a2	Add missing conversion documentation for certain encodings.	21 years ago
Bruce Momjian	e42e3b6c56	Reorder documented encodings to be alphabetical. ... Remove warning about pre-7.2 LATIN5 usage.	21 years ago
Bruce Momjian	ee1bd33dd0	Document aliases for our supported encodings. ... Add a few encodings that were not documented.	21 years ago
Tom Lane	fa5e44017a	Adjust the API for aggregate function calls so that a C-coded function ... can tell whether it is being used as an aggregate or not. This allows such a function to avoid re-pallocing a pass-by-reference transition value; normally it would be unsafe for a function to scribble on an input, but in the aggregate case it's safe to reuse the old transition value. Make int8inc() do this. This gets a useful improvement in the speed of COUNT(*), at least on narrow tables (it seems to be swamped by I/O when the table rows are wide). Per a discussion in early December with Neil Conway. I also fixed int_aggregate.c to check this, thereby turning it into something approaching a supportable technique instead of being a crude hack.	21 years ago
Bruce Momjian	852ef58da9	Documention all our supported encodings.	21 years ago
Bruce Momjian	b9de4a26cf	Here's the patch to fix a lot of markup errors in the HTML FAQs. Doesn't ... change content (at least not supposed to). Magnus Hagander	21 years ago
Bruce Momjian	db48396a8a	Fix typos. ... Hashem Masoud	21 years ago
Bruce Momjian	85ecedf1d8	Fix typos. ... Robert Treat	21 years ago
Bruce Momjian	7e3a8d9a83	Fix typo.	21 years ago
Tom Lane	595ed2a855	Make the behavior of HAVING without GROUP BY conform to the SQL spec. ... Formerly, if such a clause contained no aggregate functions we mistakenly treated it as equivalent to WHERE. Per spec it must cause the query to be treated as a grouped query of a single group, the same as appearance of aggregate functions would do. Also, the HAVING filter must execute after aggregate function computation even if it itself contains no aggregate functions.	21 years ago