aboutsummaryrefslogtreecommitdiff
path: root/doc/src
Commit message (Collapse)AuthorAge
* Add:Bruce Momjian2005-05-10
| | | | | > * Allow postgresql.conf values to be set so they can not be changed by > the user
* Done:Bruce Momjian2005-05-10
| | | | | | | | < * Add session start time and last statement time to pg_stat_activity > * -Add session start time and last statement time to pg_stat_activity 134c134 < * Add the client IP address and port to pg_stat_activity > * -Add the client IP address and port to pg_stat_activity
* Rename encryption section.Bruce Momjian2005-05-09
|
* Remove encryption FAQ item now that we have a doc section.Bruce Momjian2005-05-09
|
* Improve wording of new documentation section on encryption, and move itBruce Momjian2005-05-09
| | | | a few sections up.
* Complete the following TODO items:Neil Conway2005-05-09
| | | | | | | | | * Add session start time to pg_stat_activity * Add the client IP address and port to pg_stat_activity Original patch from Magnus Hagander, code review by Neil Conway. Catalog version bumped. This patch sends the client IP address and port number in every statistics message; that's not ideal, but will be fixed up shortly.
* Update release notes for upcoming re-releases.Tom Lane2005-05-09
|
* Add encryption section to documentation.Bruce Momjian2005-05-08
| | | | Christopher Browne
* Documentation adjustments.Bruce Momjian2005-05-08
| | | | Vladimir Chukharev
* Add description:Bruce Momjian2005-05-07
| | | | | | | | < Currently locale can only be set during initdb. > Currently locale can only be set during initdb. No global tables have > locale-aware columns. However, the database template used during > database creation might have locale-aware indexes. The indexes would > need to be reindexed to match the new locale.
* Done:Bruce Momjian2005-05-07
| | | | > o -Allow COPY to optionally include column headings in the first line
* Add items:Bruce Momjian2005-05-07
| | | | | | | | | | | | | | | | | | | | | | > * Prevent to_char() on interval from returning meaningless values > > For example, to_char('1 month', 'mon') is meaningless. Basically, > most date-related parameters to to_char() are meaningless for > intervals because interval is not anchored to a date. > > * Allow to_char() on interval values to accumulate the highest unit > requested > > o to_char(INTERVAL '1 hour 5 minutes', 'MI') => 65 > o to_char(INTERVAL '43 hours 20 minutes', 'MI' ) => 2600 > o to_char(INTERVAL '43 hours 20 minutes', 'WK:DD:HR:MI') => 0:1:19:20 > o to_char(INTERVAL '3 years 5 months','MM') => 41 > > Some special format flag would be required to request such > accumulation. Such functionality could also be added to EXTRACT. > Prevent accumulation that crosses the month/day boundary because of > the uneven number of days in a month. >
* Add COPY WITH CVS HEADER to allow a heading line as the first line inBruce Momjian2005-05-07
| | | | | | COPY. Andrew Dunstan
* Adjust question spacing.Bruce Momjian2005-05-06
|
* Update misleading comment about the use of lanpltrusted ... it isTom Lane2005-05-06
| | | | significant regardless of the value of lanispl.
* Remove documentation that CSV didn't handle carriage returns and lineBruce Momjian2005-05-06
| | | | feeds properly.
* Per core discussion, we should push out a 7.2.* release too whileTom Lane2005-05-05
| | | | we are at it. Add release notes.
* Update "control" item.Bruce Momjian2005-05-05
| | | | Rosser Schwarz
* Typo fix, Dave HeldBruce Momjian2005-05-05
|
* Preliminary release notes for 8.0.3, 7.4.8, 7.3.10.Tom Lane2005-05-04
|
* Alter the signature for encoding conversion functions to declare theTom Lane2005-05-03
| | | | | | output area as INTERNAL not CSTRING. This is to prevent people from calling the functions by hand. This is a permanent solution for the back branches but I hope it is just a stopgap for HEAD.
* Add FAQ on who controls the project.Bruce Momjian2005-05-02
|
* Completed:Bruce Momjian2005-05-02
| | | | | < * Remove unreferenced table files created by transactions that were > * -Check for unreferenced table files created by transactions that were
* Check the file system on postmaster startup and report any unreferencedBruce Momjian2005-05-02
| | | | | | files in the server log. Heikki Linnakangas
* Add some missing "See Also" entries to the domain-related SQL referenceNeil Conway2005-05-02
| | | | pages. From Robert Treat.
* Change SPI functions to use a `long' when specifying the number of tuplesNeil Conway2005-05-02
| | | | | | | | to produce when running the executor. This is consistent with the internal executor APIs (such as ExecutorRun), which also use a long for this purpose. It also allows FETCH_ALL to be passed -- since FETCH_ALL is defined as LONG_MAX, this wouldn't have worked on platforms where int and long are of different sizes. Per report from Tzahi Fadida.
* Change CREATE TYPE to require datatype output and send functions to haveTom Lane2005-05-01
| | | | | | | only one argument. (Per recent discussion, the option to accept multiple arguments is pretty useless for user-defined types, and would be a likely source of security holes if it was used.) Simplify call sites of output/send functions to not bother passing more than one argument.
* Fix incorrect backslashing in regexp example, per Robert Treat.Tom Lane2005-05-01
|
* Mention the actual stored size of NUMERIC values, per David Fetter.Tom Lane2005-05-01
|
* Update FAQ.Bruce Momjian2005-04-30
|
* Update replication FAQ.Bruce Momjian2005-04-30
| | | | Christopher Browne
* Done:Bruce Momjian2005-04-29
| | | | > * -Implement shared row locks and use them in RI triggers
* Implement sharable row-level locks, and use them for foreign key referencesTom Lane2005-04-28
| | | | | | | | | | | | | | | to eliminate unnecessary deadlocks. This commit adds SELECT ... FOR SHARE paralleling SELECT ... FOR UPDATE. The implementation uses a new SLRU data structure (managed much like pg_subtrans) to represent multiple- transaction-ID sets. When more than one transaction is holding a shared lock on a particular row, we create a MultiXactId representing that set of transactions and store its ID in the row's XMAX. This scheme allows an effectively unlimited number of row locks, just as we did before, while not costing any extra overhead except when a shared lock actually has to be shared. Still TODO: use the regular lock manager to control the grant order when multiple backends are waiting for a row lock. Alvaro Herrera and Tom Lane.
* Add psql \set ON_ERROR_ROLLBACK to allow statements in a transaction toBruce Momjian2005-04-28
| | | | | error without affecting the entire transaction. Valid values are "on|interactive|off".
* Wording improvement.Bruce Momjian2005-04-27
|
* Update PAM documentation, per Alvaro.Bruce Momjian2005-04-27
|
* Mention that PAM requires the user already exist in the database, perBruce Momjian2005-04-26
| | | | Dick Davies.
* Update description:Bruce Momjian2005-04-25
| | | | | | | | | | < * Allow ORDER BY ... LIMIT 1 to select high/low value without sort or > * Allow ORDER BY ... LIMIT # to select high/low value without sort or 868c868 < Right now, if no index exists, ORDER BY ... LIMIT 1 requires we sort > Right now, if no index exists, ORDER BY ... LIMIT # requires we sort 870a871 > MIN/MAX already does this, but not for LIMIT > 1.
* Re-add item with better description:Bruce Momjian2005-04-25
| | | | | | | | | | > * Allow ORDER BY ... LIMIT 1 to select high/low value without sort or > index using a sequential scan for highest/lowest values > > Right now, if no index exists, ORDER BY ... LIMIT 1 requires we sort > all values to return the high/low value. Instead The idea is to do a > sequential scan to find the high/low value, thus avoiding the sort. >
* Add description for concurrent sequential scans:Bruce Momjian2005-04-25
| | | | | | | > One possible implementation is to start sequential scans from the lowest > numbered buffer in the shared cache, and when reaching the end wrap > around to the beginning, rather than always starting sequential scans > at the start of the table.
* Update wording:Bruce Momjian2005-04-24
| | | | | | | < This allows vacuum to reclaim free space without requiring < a sequential scan > This allows vacuum to target specific pages for possible free space > without requiring a sequential scan.
* Update wording.Bruce Momjian2005-04-24
|
* Clean up HTML.Bruce Momjian2005-04-24
|
* Add replication FAQ item.Bruce Momjian2005-04-24
|
* Add line break.Bruce Momjian2005-04-24
|
* Update book items.Bruce Momjian2005-04-24
|
* Turns out our existing page size is already optimal in most cases:Bruce Momjian2005-04-23
| | | | < * Research the use of larger page sizes
* Item already added to existing 'thread' item:Bruce Momjian2005-04-23
| | | | | | | | | | < * Consider parallel processing a single query < < This would involve using multiple threads or processes to do optimization, < sorting, or execution of single query. The major advantage of such a < feature would be to allow multiple CPUs to work together to process a < single query. <
* Remove item, not sure what it refers to:Bruce Momjian2005-04-23
| | | | | | | | | < * Allow ORDER BY ... LIMIT 1 to select high/low value without sort or < index using a sequential scan for highest/lowest values < < If only one value is needed, there is no need to sort the entire < table. Instead a sequential scan could get the matching value. <
* New item:Bruce Momjian2005-04-23
| | | | > * Change WAL to use 32-bit CRC, for performance reasons
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-27 07:08:01 +0000