aboutsummaryrefslogtreecommitdiff
path: root/doc/src
Commit message (Collapse)AuthorAge
* SGML markup improvements.Neil Conway2004-02-10
|
* Add URL for most current version.Bruce Momjian2004-02-10
|
* Add mention of the developer's FAQ.Bruce Momjian2004-02-08
|
* Add mention of PostgreSQL as a community project.Bruce Momjian2004-02-08
|
* Documentation for generate_series() functions committed a few days ago.Joe Conway2004-02-05
|
* Rename SortMem and VacuumMem to work_mem and maintenance_work_mem.Tom Lane2004-02-03
| | | | | | | Make btree index creation and initial validation of foreign-key constraints use maintenance_work_mem rather than work_mem as their memory limit. Add some code to guc.c to allow these variables to be referenced by their old names in SHOW and SET commands, for backwards compatibility.
* Update char_length() example for new semantics.Tom Lane2004-02-01
|
* Make length() disregard trailing spaces in char(n) values, per discussionTom Lane2004-02-01
| | | | | some time ago and recent patch from Gavin Sherry. Update documentation to point out that trailing spaces are insignificant in char(n).
* Improve the documentation of the 'join_collapse_limit' GUC var. Thanks toNeil Conway2004-01-27
| | | | Tom Lane for some editorial suggestions.
* The attached patch clarifies (or, rather, makes explicit) to readers howNeil Conway2004-01-26
| | | | | | to handle memory management for char pointers returned by libpq functions. Original patch by Gavin Sherry, some tweaking and consistency improvements by Neil Conway.
* Add usage examples for PREPARE and EXECUTE. Original patch from GavinNeil Conway2004-01-26
| | | | Sherry, editorializing by Neil Conway.
* Clarify that the 'user' column still applies for 'trust'.Bruce Momjian2004-01-26
|
* Update datestamp.Bruce Momjian2004-01-26
|
* *** empty log message ***Bruce Momjian2004-01-25
|
* Fix typo I mistakenly added.Bruce Momjian2004-01-25
|
* Update null storage description.Bruce Momjian2004-01-25
|
* Mention that log_statement only prints query on PREPARE, not EXECUTE,Bruce Momjian2004-01-25
| | | | and PL/pgSQL only prints queries on first function call.
* Support named parameters in information_schema.parameters,Tom Lane2004-01-24
| | | | | per Dennis Bjorklund. I did not force initdb for this, but you'd need to do one to get the improved view.
* Fix problems with dropped columns in pltcl triggers, per report from Patrick ↵Tom Lane2004-01-24
| | | | Samson.
* Example of a function taking a composite type should show how to call it.Tom Lane2004-01-24
|
* Revise GEQO planner to make use of some heuristic knowledge about SQL, namelyTom Lane2004-01-23
| | | | | | | | | | | | | | that it's good to join where there are join clauses rather than where there are not. Also enable it to generate bushy plans at need, so that it doesn't fail in the presence of multiple IN clauses containing sub-joins. These changes appear to improve the behavior enough that we can substantially reduce the default pool size and generations count, thereby decreasing the runtime, and yet get as good or better plans as we were getting in 7.4. Consequently, adjust the default GEQO parameters. I also modified the way geqo_effort is used so that it affects both population size and number of generations; it's now useful as a single control to adjust the GEQO runtime-vs-plan-quality tradeoff. Bump geqo_threshold to 12, since even with these changes GEQO seems to be slower than the regular planner at 11 relations.
* Add MySQL mention of licensing difference.Bruce Momjian2004-01-23
|
* Minor improvements to the trigger documentation, and a few SGML fixes.Neil Conway2004-01-22
|
* Repair error apparently introduced in the initial coding of GUC: theTom Lane2004-01-21
| | | | | | default value for geqo_effort is supposed to be 40, not 1. The actual 'genetic' component of the GEQO algorithm has been practically disabled since 7.1 because of this mistake. Improve documentation while at it.
* Implement '\copy from -' to support reading copy data from the sameTom Lane2004-01-20
| | | | | | source the \copy came from. Also, fix prompting logic so that initial and per-line prompts appear for all cases of reading from an interactive terminal. Patch by Mark Feit, with some kibitzing by Tom Lane.
* Remove no-longer-relevant note about forcing the type of an integerTom Lane2004-01-20
| | | | constant. Per Kris Jurka.
* This is a patch to support readline prompts which contain non-printingTom Lane2004-01-20
| | | | | | | characters, as for fancy colorized prompts. This was nearly a direct lift from bash-2.05b's lib/readline/display.c, per guidance from Chet Ramey. Reece Hart
* Remove JDBC from the build system and documentation, too.Tom Lane2004-01-19
|
* Improve discussion of consistent-snapshot backup technique. HaphazardTom Lane2004-01-19
| | | | | editing of this text had left nearly contradictory statements in adjacent paragraphs ...
* Some refinement of XSLT processing: The result now looks just about as goodPeter Eisentraut2004-01-15
| | | | as the result of the SGML-based tool chain.
* Make rule and stylesheet to try out XSLT for DocBook processingPeter Eisentraut2004-01-13
|
* Put See Also links back in alphabetical order.Peter Eisentraut2004-01-11
|
* Minor documentation improvements.Neil Conway2004-01-11
|
* Add CREATE TRIGGER, CREATE INDEX, and CREATE SEQUENCE to the list ofNeil Conway2004-01-11
| | | | | | | expressions supported by CREATE SCHEMA. Also added the beginning of some regression tests for CREATE SCHEMA; plenty more work is needed here.
* Implement "WITH / WITHOID OIDS" clause for CREATE TABLE AS. This isNeil Conway2004-01-10
| | | | | | | | | | intended to allow application authors to insulate themselves from changes to the default value of 'default_with_oids' in future releases of PostgreSQL. This patch also fixes a bug in the earlier implementation of the 'default_with_oids' GUC variable: code in gram.y should not examine the value of GUC variables directly due to synchronization issues.
* Allow BEGIN WORK to specify transaction isolation level, like STARTBruce Momjian2004-01-10
| | | | TRANSACTION.
* Allow libpq to do thread-safe SIGPIPE handling. This allows it toBruce Momjian2004-01-09
| | | | | | | | ignore SIGPIPE from send() in libpq, but terminate on any other SIGPIPE, unless the user installs their own signal handler. This is a minor fix because the only time you get SIGPIPE from libpq's send() is when the backend dies.
* German FAQ update.Bruce Momjian2004-01-09
| | | | Ian Barwick
* Update Russian FAQ.Bruce Momjian2004-01-08
| | | | Viktor Vislobokov
* Apply the core parts of Dennis Bjorklund's patch to allow functionTom Lane2004-01-06
| | | | | | | | | parameters to be declared with names. pg_proc has a column to store names, and CREATE FUNCTION can insert data into it, but that's all as yet. I need to do more work on the pg_dump and plpgsql portions of the patch before committing those, but I thought I'd get the bulky changes in before the tree drifts under me. initdb forced due to pg_proc change.
* Favor Freenode rather than EFnet in IRC listing. Freenode is more popular.Bruce Momjian2004-01-06
|
* Make the 'wal_debug' GUC variable a boolean (rather than an integer), andNeil Conway2004-01-06
| | | | hide it behind #ifdef WAL_DEBUG blocks.
* Remove an old and out-of-date SGML comment from this file: we alreadyNeil Conway2004-01-05
| | | | have WAL, outer joins, and TOAST.
* Fix (yet another) instance of incorrect markup for a GUC variable.Neil Conway2004-01-05
|
* Update for 7.4.1 as newest version.Bruce Momjian2004-01-05
|
* Correct gettext URL.Peter Eisentraut2004-01-04
|
* Recommend SHOW, instead of pg_controldata, for checking LC_COLLATE andTom Lane2003-12-30
| | | | LC_CTYPE settings of a database.
* Be a little more consistent about which terms are uppercased inTom Lane2003-12-26
| | | | index entries.
* Fixed docs to clearly note that ecpg is originally a C precompiler and C++ ↵Michael Meskes2003-12-26
| | | | stuff is not 100%.
* > > I have no idea if this in Oracle or not. But it's something IBruce Momjian2003-12-25
| | | | | | | | | | | | | | | > > needed, and other people in the past asked about it too. > > It is in Oracle, but you aren't exactly on the spot. It should be > > IYYY - 4 digits ('2003') > IYY - 3 digits ('003') > IY - 2 digits ('03') > I - 1 digit ('3') Here is an updated patch that does that. Kurt Roeckx
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-06 06:36:05 +0000