aboutsummaryrefslogtreecommitdiff
path: root/doc/src
Commit message (Collapse)AuthorAge
...
* Improve documentation about foreign data wrapper validator functions.Tom Lane2011-07-05
| | | | Modified version of a patch by Shigeru Hanada.
* Fix typo in sslmode documentationMagnus Hagander2011-07-05
| | | | Per bug #6089, noted by Sidney Cadot
* Small documentation tweaksPeter Eisentraut2011-07-05
|
* Set user_defined_types.data_type to nullPeter Eisentraut2011-07-04
| | | | | On re-reading the standard, this field is only used for distinct or reference types.
* Clarify that you need ActiveState perl 5.8 *or later* to build on Windows.Heikki Linnakangas2011-07-04
|
* Remove silent_mode. You get the same functionality with "pg_ctl -lHeikki Linnakangas2011-07-04
| | | | | | | | | postmaster.log", or nohup. There was a small issue with LINUX_OOM_ADJ and silent_mode, namely that with silent_mode the postmaster process incorrectly used the OOM settings meant for backend processes. We certainly could've fixed that directly, but since silent_mode was redundant anyway, we might as well just remove it.
* Reset ALTER TABLE lock levels to AccessExclusiveLock in all cases.Simon Riggs2011-07-04
| | | | | Locks on inheritance parent remain at lower level, as they were before. Remove entry from 9.1 release notes.
* Fix omissions in documentation of the pg_roles view.Tom Lane2011-07-03
| | | | | | | Somehow, column rolconfig got removed from the documentation of the pg_roles view in the 9.0 cycle, although the column is actually still there. In 9.1, we'd also forgotten to document the rolreplication column. Spotted by Sakamoto Masahiko.
* In the pg_upgrade docs, move 50432 port mention to the place where weBruce Momjian2011-07-01
| | | | talk about client access.
* Change pg_upgrade to use port 50432 by default to avoid unintendedBruce Momjian2011-07-01
| | | | | client connections during the upgrade. Also rename data/bin/port environment variables to being with 'PG'. Also no longer honor PGPORT.
* Enable CHECK constraints to be declared NOT VALIDAlvaro Herrera2011-06-30
| | | | | | | | | | | | | | | | | | | | | | | This means that they can initially be added to a large existing table without checking its initial contents, but new tuples must comply to them; a separate pass invoked by ALTER TABLE / VALIDATE can verify existing data and ensure it complies with the constraint, at which point it is marked validated and becomes a normal part of the table ecosystem. An non-validated CHECK constraint is ignored in the planner for constraint_exclusion purposes; when validated, cached plans are recomputed so that partitioning starts working right away. This patch also enables domains to have unvalidated CHECK constraints attached to them as well by way of ALTER DOMAIN / ADD CONSTRAINT / NOT VALID, which can later be validated with ALTER DOMAIN / VALIDATE CONSTRAINT. Thanks to Thom Brown, Dean Rasheed and Jaime Casanova for the various reviews, and Robert Hass for documentation wording improvement suggestions. This patch was sponsored by Enova Financial.
* Unify spelling of "canceled", "canceling", "cancellation"Peter Eisentraut2011-06-29
| | | | | We had previously (af26857a2775e7ceb0916155e931008c2116632f) established the U.S. spellings as standard.
* Implement the collation columns of various information schema viewsPeter Eisentraut2011-06-28
| | | | | | Fill in the collation columns of the views attributes, columns, domains, and element_types. Also update collation information in sql_implementation_info.
* Add composite-type attributes to information_schema.element_types viewPeter Eisentraut2011-06-28
|
* Mention that SSPI authentication can use GSSAPI on non-Windows systems.Robert Haas2011-06-27
| | | | As noted by Christian Ullrich.
* Documentation improvements for pg_locks with respect to SSI.Robert Haas2011-06-24
| | | | | | | Explain that querying pg_locks does not simultaneously lock both the normal lock manager and the predicate lock manager. Per discussion with Kevin Grittner.
* In pg_upgrade docs, clarify that link mode uses "hard" links.Bruce Momjian2011-06-23
| | | | Backpatch to 9.1 and 9.0.
* Add information schema views role_udt_grants, udt_privileges, user_defined_typesPeter Eisentraut2011-06-23
|
* Add a bit of markupPeter Eisentraut2011-06-23
|
* Add smallserial pseudotype.Robert Haas2011-06-21
| | | | | | | This is just like serial and bigserial, except it generates an int2 column rather than int4 or int8. Mike Pultz, reviewed by Brar Piening and Josh Kupershmidt
* Make deadlock_timeout PGC_SUSET rather than PGC_SIGHUP.Robert Haas2011-06-21
| | | | | | | | | | | | | | | | | This allows deadlock_timeout to be reduced for transactions that are particularly likely to be involved in a deadlock, thus detecting it more quickly. It is also potentially useful as a poor-man's deadlock priority mechanism: a transaction with a high deadlock_timeout is less likely to be chosen as the victim than one with a low deadlock_timeout. Since that could be used to game the system, we make this PGC_SUSET rather than PGC_USERSET. At some point, it might be worth thinking about a more explicit priority mechanism, since using this is far from fool-proof. But let's see whether there's enough use case to justify the additional work before we go down that route. Noah Misch, reviewed by Shigeru Hanada
* Add notion of a "transform function" that can simplify function calls.Robert Haas2011-06-21
| | | | | | | | | | Initially, we use this only to eliminate calls to the varchar() function in cases where the length is not being reduced and, therefore, the function call is equivalent to a RelabelType operation. The most significant effect of this is that we can avoid a table rewrite when changing a varchar(X) column to a varchar(Y) column, where Y > X. Noah Misch, reviewed by me and Alexey Klyukin
* Performance tuning advice for SSI.Robert Haas2011-06-21
| | | | Kevin Grittner, with additional wordsmithing by me.
* Fix missed use of "cp -i" in an example, per Fujii Masao.Tom Lane2011-06-20
| | | | Also be more careful about markup: use & not just &.
* Produce HISTORY file consistently as ASCIIPeter Eisentraut2011-06-19
| | | | | | | | The release notes may contain non-ASCII characters (for contributor names), which lynx converts to the encoding determined by the current locale. The get output that is deterministic and easily readable by everyone, we make lynx produce LATIN1 and then convert that to ASCII with transliteration for the non-ASCII characters.
* Capitalization fixesPeter Eisentraut2011-06-19
|
* Don't use "cp -i" in the example WAL archive_command.Tom Lane2011-06-17
| | | | | | | | | | | | | | This is a dangerous example to provide because on machines with GNU cp, it will silently do the wrong thing and risk archive corruption. Worse, during the 9.0 cycle somebody "improved" the discussion by removing the warning that used to be there about that, and instead leaving the impression that the command would work as desired on most Unixen. It doesn't. Try to rectify the damage by providing an example that is safe most everywhere, and then noting that you can try cp -i if you want but you'd better test that. In back-patching this to all supported branches, I also added an example command for Windows, which wasn't provided before 9.0.
* Fix typo.Robert Haas2011-06-17
| | | | Per Josh Kupershmidt and Tom Lane.
* Rework parsing of ConstraintAttributeSpec to improve NOT VALID handling.Tom Lane2011-06-15
| | | | | | | | | | | The initial commit of the ALTER TABLE ADD FOREIGN KEY NOT VALID feature failed to support labeling such constraints as deferrable. The best fix for this seems to be to fold NOT VALID into ConstraintAttributeSpec. That's a bit more general than the documented syntax, but it allows better-targeted syntax error messages. In addition, do some mostly-but-not-entirely-cosmetic code review for the whole NOT VALID patch.
* Document that psql's \d also works with composite typesPeter Eisentraut2011-06-14
| | | | This has always been true, it was just never documented.
* In pg_upgrade, document that link mode has to have data directories onBruce Momjian2011-06-14
| | | | | | | | | the same file system, and that authentication should lock out normal users. Per suggestsion from #postgresql irc channel. Backpatch to 9.1.
* Fix grammatical mistake introduced by previous commitAlvaro Herrera2011-06-14
| | | | Per note from Tom
* Mention DROP TABLE as well as ALTER TABLE NO INHERITAlvaro Herrera2011-06-14
| | | | | | | | | ... when talking about how good they are in replacement of bulk DELETE in partitioned setups. The original wording was a bit confusing. Per an observation from David Wheeler.
* Improve accuracy of ON_ERROR_STOP documentation.Robert Haas2011-06-14
| | | | Per a gripe from Tom Lane.
* Document that bits to the right of the CIDR mask "should" be zero, notBruce Momjian2011-06-13
| | | | "must".
* Expand warnings on locks acquired by CREATE INDEX CONCURRENTLYAlvaro Herrera2011-06-13
| | | | | | | | | The previous wording wasn't explicit enough, which could misled readers into thinking that the locks acquired are more restricted in nature than they really are. The resulting optimism can be damaging to morale when confronted with reality, as has been observed in the field. Greg Smith
* Remove parentheses from mention of current_schemas function.Robert Haas2011-06-13
| | | | | | | This is more consistent with what we do elsewhere, and hopefully avoids creating the perception that current_schemas takes no arguments. As suggested by Brendan Jurd
* Clarify that NATURAL without matching columns is like CROSS JOIN.Robert Haas2011-06-13
| | | | As suggested by Grzegorz Szpetkowski.
* Add doc cross-reference to search_path discussion of current_schemas().Robert Haas2011-06-13
| | | | Brendan Jurd
* Document GUC context for synchronous_standby_names/hot_standby_feedback.Robert Haas2011-06-13
| | | | Fujii Masao
* In ALTER EXTENSION docs, document left_type/right_type.Robert Haas2011-06-13
| | | | Noted by Daniele Varrazzo.
* Markup fix.Robert Haas2011-06-13
| | | | Fujii Masao
* More foreign table documentation improvements.Robert Haas2011-06-13
| | | | Shigeru Hanada, with some additional wordsmithing by me
* Corrections to ALTER FOREIGN TABLE documentation.Robert Haas2011-06-12
| | | | Shigeru Hanada, with a minor grammar correction.
* Ecpg doc cleanups, as reported by Marc Cousin.Bruce Momjian2011-06-09
|
* Update 9.1 release notes to reflect commits through today.Tom Lane2011-06-09
| | | | Also do some desultory copy-editing on the notes.
* Support silent mode for service registrations on win32Magnus Hagander2011-06-09
| | | | | | | | Using -s when registering a service will now suppress the application eventlog entries stating that the service is starting and started. MauMau
* Fix documentation of information_schema.element_typesPeter Eisentraut2011-06-09
| | | | | | | | | | | The documentation of the columns collection_type_identifier and dtd_identifier was wrong. This effectively reverts commits 8e1ccad51901e83916dae297cd9afa450957a36c and 57352df66d3a0885899d39c04c067e63c7c0ba30 and updates the name array_type_identifier (the name in SQL:1999) to collection_type_identifier. closes bug #5926
* Make citext's equality and hashing functions collation-insensitive.Tom Lane2011-06-08
| | | | | | | | | | | | | | This is an ugly hack to get around the fact that significant parts of the core backend assume they don't need to worry about passing collation to equality and hashing functions. That's true for the core string datatypes, but citext should ideally have equality behavior that depends on the specified collation's LC_CTYPE. However, there's no chance of fixing the core before 9.2, so we'll have to live with this compromise arrangement for now. Per bug #6053 from Regina Obe. The code changes in this commit should be reverted in full once the core code is up to speed, but be careful about reverting the docs changes: I fixed a number of obsolete statements while at it.
* Reorder pg_ctl promote after pg_ctl statusPeter Eisentraut2011-06-08
| | | | | | | | | | | | Since start/stop/restart/reload/status is a kind of standard command set, it seems odd to insert the special-purpose "promote" in between the closely related "restart" and "reload". So put it after "status" in code and documentation. Put the documentation of the -U option in some sensible place. Rewrite the synopsis sentence in help and documentation to make it less of a growing mouthful.
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-01 16:01:43 +0000