aboutsummaryrefslogtreecommitdiff
path: root/doc/src/sgml
Commit message (Collapse)AuthorAge
* Rename encryption 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 COPY WITH CVS HEADER to allow a heading line as the first line inBruce Momjian2005-05-07
| | | | | | COPY. Andrew Dunstan
* 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.
* 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.
* 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
|
* 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.
* Add documentation stating how to determine if FSM settings are too lowBruce Momjian2005-04-23
| | | | --- look at a database-wide VACUUM VERBOSE.
* Typo fix. Alvaro.Bruce Momjian2005-04-22
|
* Remove pre-7.3 mention that FOR UPDATE can be before LIMIT.Bruce Momjian2005-04-22
| | | | | Document that FOR UPDATE and LIMIT together can return fewer rows that LIMIT specifies, and why.
* Clarify that only crypt can't use md5 pg_shadow passwords.Bruce Momjian2005-04-22
|
* Clarify use of MD5 authentication and pg_shadow encryption.Bruce Momjian2005-04-21
|
* Rethink original decision to use AND/OR Expr nodes to represent bitmapTom Lane2005-04-21
| | | | | | | logic operations during planning. Seems cleaner to create two new Path node types, instead --- this avoids duplication of cost-estimation code. Also, create an enable_bitmapscan GUC parameter to control use of bitmap plans.
* Add note clarifying that indexes that support ordered scans had betterTom Lane2005-04-20
| | | | allow clauseless scans.
* >>>>Luckily, PG 8 is available for this. Do you have a short example?Bruce Momjian2005-04-19
| | | | | | | | | | | | | | | >>> >>>No, and I think it should be in the manual as an example. >>> >>>You will need to enter a loop that uses exception handling to detect >>>unique_violation. >> >>Pursuant to an IRC discussion to which Dennis Bjorklund and >>Christopher Kings-Lynne made most of the contributions, please find >>enclosed an example patch demonstrating an UPSERT-like capability. >> David Fetter
* > >Luckily, PG 8 is available for this. Do you have a short example?Bruce Momjian2005-04-19
| | | | | | | | | | | | | | > > No, and I think it should be in the manual as an example. > > You will need to enter a loop that uses exception handling to detect > unique_violation. Pursuant to an IRC discussion to which Dennis Bjorklund and Christopher Kings-Lynne made most of the contributions, please find enclosed an example patch demonstrating an UPSERT-like capability. David Fetter
* Update PITR wording, per Simon.Bruce Momjian2005-04-19
|
* Update PITR setence to mention WAL and file system dump.Bruce Momjian2005-04-18
|
* Add description that WAL files used during backup have to be archivedBruce Momjian2005-04-18
| | | | before you are done.
* Update PITR mention of which WAL files are needed.Bruce Momjian2005-04-18
|
* Clarify name of file to be checked for PITR expiring.Bruce Momjian2005-04-17
|
* Minor improvements to locale documentation.Tom Lane2005-04-16
|
* First phase of project to use fixed OIDs for all system catalogs andTom Lane2005-04-14
| | | | | | | | | | | | | | | | indexes. Extend the macros in include/catalog/*.h to carry the info about hand-assigned OIDs, and adjust the genbki script and bootstrap code to make the relations actually get those OIDs. Remove the small number of RelOid_pg_foo macros that we had in favor of a complete set named like the catname.h and indexing.h macros. Next phase will get rid of internal use of names for looking up catalogs and indexes; but this completes the changes forcing an initdb, so it looks like a good place to commit. Along the way, I made the shared relations (pg_database etc) not be 'bootstrap' relations any more, so as to reduce the number of hardwired entries and simplify changing those relations in future. I'm not sure whether they ever really needed to be handled as bootstrap relations, but it seems to work fine to not do so now.
* Simplify initdb-time assignment of OIDs as I proposed yesterday, andTom Lane2005-04-13
| | | | | | | | avoid encroaching on the 'user' range of OIDs by allowing automatic OID assignment to use values below 16k until we reach normal operation. initdb not forced since this doesn't make any incompatible change; however a lot of stuff will have different OIDs after your next initdb.
* Minor consistency improvement to the documentation on array functions.Neil Conway2005-04-13
|
* Add aggsortop column to pg_aggregate, so that MIN/MAX optimization canTom Lane2005-04-12
| | | | | | | | be supported for all datatypes. Add CREATE AGGREGATE and pg_dump support too. Add specialized min/max aggregates for bpchar, instead of depending on text's min/max, because otherwise the possible use of bpchar indexes cannot be recognized. initdb forced because of catalog changes.
* Fix broken markup.Tom Lane2005-04-12
|
* We don't put URL's in ulink's because the URL is always generated, butBruce Momjian2005-04-09
| | | | | | we can put words in ulink and the URL will still be printed. per Peter
* Change the default setting of "add_missing_from" to false. This has beenNeil Conway2005-04-08
| | | | | | the long-term plan for this behavior for quite some time, but it is only possible now that DELETE has a USING clause so that the user can join other tables in a DELETE statement without relying on this behavior.
* Update and copy-edit release notes for 8.0.2.Tom Lane2005-04-07
|
* Allow plpgsql functions to omit RETURN command when the function returnsTom Lane2005-04-07
| | | | | | output parameters or VOID or a set. There seems no particular reason to insist on a RETURN in these cases, since the function return value is determined by other elements anyway. Per recent discussion.
* Minor documentation tweak.Neil Conway2005-04-07
|
* Add a "USING" clause to DELETE, which is equivalent to the FROM clauseNeil Conway2005-04-07
| | | | | | | | | | | | | | | in UPDATE. We also now issue a NOTICE if a query has _any_ implicit range table entries -- in the past, we would only warn about implicit RTEs in SELECTs with at least one explicit RTE. As a result of the warning change, 25 of the regression tests had to be updated. I also took the opportunity to remove some bogus whitespace differences between some of the float4 and float8 variants. I believe I have correctly updated all the platform-specific variants, but let me know if that's not the case. Original patch for DELETE ... USING from Euler Taveira de Oliveira, reworked by Neil Conway.
* Adjust grammar for plpgsql's OPEN command so that a cursor can beTom Lane2005-04-05
| | | | | | | OPENed on non-SELECT commands such as EXPLAIN or SHOW (anything that returns tuples is allowed). This flexibility already existed for bound cursors, but OPEN was artificially restricting what it would take. Per a gripe some months back.
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-31 02:59:10 +0000