aboutsummaryrefslogtreecommitdiff
path: root/doc/src
Commit message (Collapse)AuthorAge
...
* Fix typo: PGTYPES_NUM_OVERFLOW should be PGTYPES_NUM_UNDERFLOW.Tom Lane2010-05-09
| | | | Noted by KOIZUMI Satoru.
* Fix incorrect parameter tag in docs, spotted by KOIZUMI Satoru.Heikki Linnakangas2010-05-05
|
* Remove spurious dot, per bug #5446 reported by koizumistr@minos.ocn.ne.jpAlvaro Herrera2010-05-03
|
* Change wording so that you don't need to understand that wal_levelsHeikki Linnakangas2010-05-03
| | | | form a hierarchy. Per Simon's suggestion.
* Change "literal" tag to the more appropriate "firstterm", when describingHeikki Linnakangas2010-05-03
| | | | what "eventually consistent" means.
* Add cross-reference from wal_level to hot_standby setting. UpdateHeikki Linnakangas2010-05-03
| | | | | the PITR documentation to mention that you need to set wal_level to 'archive' or 'hot_standby', to enable WAL archiving. Per Simon's request.
* Docs for standbycheck regression tests.Simon Riggs2010-05-02
|
* Mention that max_standby_delay has units of milliseconds. Units are mentionedSimon Riggs2010-05-02
| | | | for all other parameters where the default is expressed in a different unit.
* Clean up some awkward, inaccurate, and inefficient processing aroundTom Lane2010-05-02
| | | | | | | | | | | | MaxStandbyDelay. Use the GUC units mechanism for the value, and choose more appropriate timestamp functions for performing tests with it. Make the ps_activity manipulation in ResolveRecoveryConflictWithVirtualXIDs have behavior similar to ps_activity code elsewhere, notably not updating the display when update_process_title is off and not truncating the display contents at an arbitrarily-chosen length. Improve the docs to be explicit about what MaxStandbyDelay actually measures, viz the difference between primary and standby servers' clocks, and the possible hazards if their clocks aren't in sync.
* Install hack workaround for failure of 'make all' in VPATH builds.Tom Lane2010-05-01
| | | | | | | | | It appears that gmake gets confused if postgres.sgml is not present in the working directory, and instantiates some default rule or other that would let postgres.sgml be built from postgres.xml. I haven't been able to track down exactly where that's coming from, but the problem can be dodged by specifying srcdir explicitly in the rule for postgres.xml. Per report from Vladimir Kokovic.
* Adjust postgres.xml rule so that make will notice a failure exit from osx.Tom Lane2010-05-01
| | | | | | | The previous coding had it in a pipe, which on most shells won't report the error. Per experimentation with a bug report from Vladimir Kokovic. This doesn't actually fix his problem, but it does explain why make didn't report that there was a problem.
* Update our information about OS X shared memory configuration: it's nowTom Lane2010-04-30
| | | | | | | possible to set most of the SHM kernel parameters without a reboot. Also, reorder the paragraph to explain the modern configuration method first. There are probably not too many people who still care about how to do it on OS X 10.3 or older.
* Improve COPY documentation to clarify that it doesn't copy data to or fromTom Lane2010-04-30
| | | | child tables. Per gripe from Jaime Casanova.
* Documentation fix: CREATE TRIGGER 'WHERE' -> 'WHEN'Bruce Momjian2010-04-29
| | | | Selena Deckelmann
* Adjust error checks in pg_start_backup and pg_stop_backup to make it possibleTom Lane2010-04-29
| | | | | | to perform a backup without archive_mode being enabled. This gives up some user-error protection in order to improve usefulness for streaming-replication scenarios. Per discussion.
* Rename the parameter recovery_connections to hot_standby, to reduce possibleTom Lane2010-04-29
| | | | | | | | confusion with streaming-replication settings. Also, change its default value to "off", because of concern about executing new and poorly-tested code during ordinary non-replicating operation. Per discussion. In passing do some minor editing of related documentation.
* Doc fix -- last major item should not be a bullet.Bruce Momjian2010-04-29
|
* Move alpha release notes into a separate file; re-align sgml tags.Bruce Momjian2010-04-29
|
* Update 9.0 release notes to current; add major items and introductoryBruce Momjian2010-04-29
| | | | text.
* Install a workaround for 'TeX capacity exceeded' problemTom Lane2010-04-29
| | | | | | when building PDF output for recent versions of the documentation. There is probably a better answer out there somewhere, but we need something now so we can build beta releases.
* Fix typo, per Thom Brown.Tom Lane2010-04-28
|
* Modify ShmemInitStruct and ShmemInitHash to throw errors internally,Tom Lane2010-04-28
| | | | | | | | | rather than returning NULL for some-but-not-all failures as they used to. Remove now-redundant tests for NULL from call sites. We had to do something about this because many call sites were failing to check for NULL; and changing it like this seems a lot more useful and mistake-proof than adding checks to the call sites without them.
* Make pg_stats example query result a bit less wide, and add comment aboutAlvaro Herrera2010-04-28
| | | | pg_stats.inherited
* Introduce wal_level GUC to explicitly control if information needed forHeikki Linnakangas2010-04-28
| | | | | | | | | | | | | | | | | | | | | | archival or hot standby should be WAL-logged, instead of deducing that from other options like archive_mode. This replaces recovery_connections GUC in the primary, where it now has no effect, but it's still used in the standby to enable/disable hot standby. Remove the WAL-logging of "unlogged operations", like creating an index without WAL-logging and fsyncing it at the end. Instead, we keep a copy of the wal_mode setting and the settings that affect how much shared memory a hot standby server needs to track master transactions (max_connections, max_prepared_xacts, max_locks_per_xact) in pg_control. Whenever the settings change, at server restart, write a WAL record noting the new settings and update pg_control. This allows us to notice the change in those settings in the standby at the right moment, they used to be included in checkpoint records, but that meant that a changed value was not reflected in the standby until the first checkpoint after the change. Bump PG_CONTROL_VERSION and XLOG_PAGE_MAGIC. Whack XLOG_PAGE_MAGIC back to the sequence it used to follow, before hot standby and subsequent patches changed it to 0x9003.
* Add recovery.conf parameters to the documentation index, per suggestionHeikki Linnakangas2010-04-28
| | | | by Fujii Masao.
* Reformat code examples in plpgsql docs for better readability in PDF outputAlvaro Herrera2010-04-27
| | | | Erik Rijkers
* Update documentation to match pg_stat_activity changes.Tom Lane2010-04-26
|
* Document that pgpool can be used with master/slave servers to avoidBruce Momjian2010-04-26
| | | | problems with non-deterministic functions.
* When we're restricting who can connect, don't allow new walsenders.Robert Haas2010-04-26
| | | | | | | | Normal superuser processes are allowed to connect even when the database system is shutting down, or when fewer than superuser_reserved_connection slots remain. This is intended to make sure an administrator can log in and troubleshoot, so don't extend these same courtesies to users connecting for replication.
* Fix various instances of "the the".Robert Haas2010-04-23
| | | | Two of these were pointed out by Erik Rijkers; the rest I found.
* Enforce superuser permissions checks during ALTER ROLE/DATABASE SET, ratherTom Lane2010-04-21
| | | | | | | | | | | | than during define_custom_variable(). This entails rejecting an ALTER command if the target variable doesn't have a known (non-placeholder) definition, unless the calling user is superuser. When the variable *is* known, we can correctly apply the rule that only superusers can issue ALTER for SUSET parameters. This allows define_custom_variable to apply ALTER's values for SUSET parameters at module load time, secure in the knowledge that only a superuser could have set the ALTER value. This change fixes a longstanding gotcha in the usage of SUSET-level custom parameters; which is a good thing to fix now that plpgsql defines such a parameter.
* Fix pg_hba.conf matching so that replication connections only match recordsTom Lane2010-04-21
| | | | | | | | | with database = replication. The previous coding would allow them to match ordinary records too, but that seems like a recipe for security breaches. Improve the messages associated with no-such-pg_hba.conf entry to report replication connections as such, since that's now a critical aspect of whether the connection matches. Make some cursory improvements in the related documentation, too.
* Rename standby_keep_segments to wal_keep_segments.Robert Haas2010-04-20
| | | | | | Also, make the name of the GUC and the name of the backing variable match. Alnong the way, clean up a couple of slight typographical errors in the related docs.
* Update docs as to when WAL logging can be skipped.Robert Haas2010-04-20
| | | | | | | | In 8.4 and prior, WAL-logging could potentially be skipped whenever archive_mode=off. With streaming replication, this is now true only if max_wal_senders=0. Fujii Masao, with light copyediting by me
* Add an 'enable_material' GUC.Robert Haas2010-04-19
| | | | | | | | | | | The logic for determining whether to materialize has been significantly overhauled for 9.0. In case there should be any doubt about whether materialization is a win in any particular case, this should provide a convenient way of seeing what happens without it; but even with enable_material turned off, we still materialize in cases where it is required for correctness. Thanks to Tom Lane for the review.
* Provide better guidance for adjusting shared_buffers.Robert Haas2010-04-16
|
* Document that autovacuum cannot vacuum or analyze temporary tables.Bruce Momjian2010-04-16
|
* Improve punctuationPeter Eisentraut2010-04-15
|
* IP port -> TCP portPeter Eisentraut2010-04-15
| | | | backpatched to 8.1, where this first appeared
* Fix typo, spotted by Erik Rijkers.Heikki Linnakangas2010-04-15
|
* Doc change: anyways -> anyway; Erik RijkersBruce Momjian2010-04-14
|
* Add "SSD" acronym mention for solid state drive mention.Bruce Momjian2010-04-13
|
* Fix typo.Magnus Hagander2010-04-13
| | | | Fujii Masao
* Remove example of archive_command from configure section; instead haveBruce Momjian2010-04-12
| | | | | users look at the referenced section for examples, per idea from Greg Smith.
* Spell out full archive directory specification in 'test -f' continuousBruce Momjian2010-04-12
| | | | archiving example, per suggestion from Greg Smith.
* Adjust paragraph about monitoring streaming replication, now that we haveHeikki Linnakangas2010-04-12
| | | | standby_keep_segments.
* Change the logic to decide when to delete old WAL segments, so that itHeikki Linnakangas2010-04-12
| | | | | | | | | | doesn't take into account how far the WAL senders are. This way a hung WAL sender doesn't prevent old WAL segments from being recycled/removed in the primary, ultimately causing the disk to fill up. Instead add standby_keep_segments setting to control how many old WAL segments are kept in the primary. This also makes it more reliable to use streaming replication without WAL archiving, assuming that you set standby_keep_segments high enough.
* Make smart shutdown work in combination with Hot Standby/Streaming Replication.Robert Haas2010-04-08
| | | | | | | | | | At present, killing the startup process does not release any locks it holds, so we must wait to stop the startup and walreceiver processes until all read-only backends have exited. Without this patch, the startup and walreceiver processes never exit, so the server gets permanently stuck in a half-shutdown state. Fujii Masao, with review, docs, and comment adjustments by me.
* Allow quotes to be escaped in recovery.conf, by doubling them. This patchHeikki Linnakangas2010-04-07
| | | | | also makes the parsing a little bit stricter, rejecting garbage after the parameter value and values with missing ending quotes, for example.
* Forbid using pg_xlogfile_name() and pg_xlogfile_name_offset() duringHeikki Linnakangas2010-04-07
| | | | | | recovery. We might want to relax this in the future, but ThisTimeLineID isn't currently correct in backends during recovery, so the filename returned was wrong.
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-10 09:10:11 +0000