summaryrefslogtreecommitdiff
path: root/doc/src/sgml/pgupgrade.sgml
Commit message (Collapse)AuthorAgeFilesLines
* Move pg_upgrade from contrib/ to src/bin/Peter Eisentraut2015-04-141-723/+0
| | | | Reviewed-by: Michael Paquier <michael.paquier@gmail.com>
* Integrate pg_upgrade_support module into backendPeter Eisentraut2015-04-141-3/+2
| | | | | | | | | | | | | | | | Previously, these functions were created in a schema "binary_upgrade", which was deleted after pg_upgrade was finished. Because we don't want to keep that schema around permanently, move them to pg_catalog but rename them with a binary_upgrade_... prefix. The provided functions are only small wrappers around global variables that were added specifically for pg_upgrade use, so keeping the module separate does not create any modularity. The functions still check that they are only called in binary upgrade mode, so it is not possible to call these during normal operation. Reviewed-by: Michael Paquier <michael.paquier@gmail.com>
* pg_upgrade: document use of rsync for slave upgradesBruce Momjian2015-03-181-11/+148
| | | | | | | Also document that rsync has one-second granularity for file change comparisons. Report by Stephen Frost
* pg_upgrade docs: update docs for 8.3 support removalBruce Momjian2014-08-251-82/+2
|
* pg_ctl, pg_upgrade: allow multiple -o/-O options, append themBruce Momjian2014-08-251-2/+4
| | | | Report by Pavel Raiskup
* pg_upgrade: assume user is install userBruce Momjian2014-08-041-1/+1
| | | | | | The user specified to the upgrade was effectively the install user, but that was not clearly stated in the comments, documentation, or error messages.
* Limit pg_upgrade authentication advice to always-secure techniques.Noah Misch2014-07-181-8/+6
| | | | | | | ~/.pgpass is a sound choice everywhere, and "peer" authentication is safe on every platform it supports. Cease to recommend "trust" authentication, the safety of which is deeply configuration-specific. Back-patch to 9.0, where pg_upgrade was introduced.
* docs: small adjustements to recent SELECT and pg_upgrade improvementsBruce Momjian2014-03-081-4/+4
|
* pg_upgrade: document delete problems with tablespaces inside the cluster ↵Bruce Momjian2014-03-071-1/+2
| | | | | | directory Per report by Marc Mamin
* doc: Improve DocBook XML validityPeter Eisentraut2014-02-231-4/+4
| | | | | | | | | | | DocBook XML is superficially compatible with DocBook SGML but has a slightly stricter DTD that we have been violating in a few cases. Although XSLT doesn't care whether the document is valid, the style sheets don't necessarily process invalid documents correctly, so we need to work toward fixing this. This first commit moves the indexterms in refentry elements to an allowed position. It has no impact on the output.
* pg_upgrade: mention the need for tablespace snapshots in docsBruce Momjian2014-02-131-3/+4
|
* pg_upgrade: document use of file system and COW snapshotsBruce Momjian2014-02-121-1/+4
|
* Rename 'gmake' to 'make' in docs and recommended commandsBruce Momjian2014-02-121-1/+1
| | | | This simplifies the docs and makes it easier to cut/paste command lines.
* pg_upgrade doc: link mode additionsBruce Momjian2013-10-051-2/+4
| | | | | | | Mention that link mode uses less disk space, and uses junction points on Windows. Backpatch to 9.3.
* pg_upgrade docs: don't use cluster for binary/libBruce Momjian2013-07-261-3/+4
| | | | | | In a few cases, pg_upgrade said old/new cluster location when it meant old/new Postgres install location, so fix those. Per private email report
* pg_upgrade: document possible pg_hba.conf optionsBruce Momjian2013-07-111-4/+4
| | | | | | | | Previously, pg_upgrade docs recommended using .pgpass if using MD5 authentication to avoid being prompted for a password. Turns out pg_ctl never prompts for a password, so MD5 requires .pgpass --- document that. Also recommend 'peer' for authentication too. Backpatch back to 9.1.
* pg_upgrade: document link optionsBruce Momjian2013-07-071-1/+2
| | | | | | Document that tablespaces and pg_xlog can be on different file systems for pg_upgrade --link mode. Backpatch to 9.3.
* pg_upgrade: remove -h optionBruce Momjian2013-06-281-1/+0
| | | | | -h (help) is not needed; pg_upgrade already supports --help and -?, which is consistent with other tools.
* pg_upgrade: trim down --help and doc option descriptionsBruce Momjian2013-06-281-14/+14
| | | | | | Previous code had old/new prefixes on option values, e.g. --old-datadir=OLDDATADIR. Remove them, for simplicity; now: --old-datadir=DATADIR. Also update docs to do the same.
* pg_upgrade: change -u to -U, for consistencyBruce Momjian2013-06-281-2/+2
| | | | | | | Change -u (user) option to -U, for consistency with other tools like pg_dump and psql. Also expand --user to --username, again for consistency. BACKWARD INCOMPATIBILITY
* pg_upgrade: document that --link should be used with --checkBruce Momjian2013-06-061-1/+3
| | | | Backpatch to 9.2.
* pg_upgrade docs: mention need to set parameters for vacuumdb.Bruce Momjian2013-05-281-1/+2
|
* pg_upgrade docs: give tips on automationBruce Momjian2013-05-091-1/+5
| | | | | | Document that post-upgrade steps are likely to be the same for all clusters with the same DDL/schemas; this should help automated upgrades.
* Update the description for the graphical installersMagnus Hagander2013-04-101-5/+5
| | | | | Remove references to "one click", as we're not supposed to call them that anymore.
* pg_upgrade docs: mention modification of postgresql.conf in new clusterBruce Momjian2013-01-311-1/+3
| | | | | | | | | Mention it might be necessary to modify postgresql.conf in the new cluster to match the old cluster. Backpatch to 9.2. Suggested by user.
* Allow parallel copy/link in pg_upgradeBruce Momjian2013-01-091-4/+5
| | | | | This patch implements parallel copying/linking of files by tablespace using the --jobs option in pg_upgrade.
* Add pg_upgrade --jobs parameterBruce Momjian2012-12-261-3/+15
| | | | | Add pg_upgrade --jobs, which allows parallel dump/restore of databases, which improves performance.
* In pg_upgrade docs, mention using base backup as part of rsync forBruce Momjian2012-11-071-1/+4
| | | | | | logical replication upgrades. Backpatch to 9.2.
* Document that pg_upgrade requires PGHOST be set for any pre-9.1 serversBruce Momjian2012-09-041-5/+4
| | | | | | with a socket directory mismatch with the new server. Backpatch to 9.2.
* Fix pg_upgrade to cope with non-default unix_socket_directory scenarios.Tom Lane2012-09-031-0/+8
| | | | | | | | | | | | | | | | | | | | | | When starting either an old or new postmaster, force it to place its Unix socket in the current directory. This makes it even harder for accidental connections to occur during pg_upgrade, and also works around some scenarios where the default socket location isn't usable. (For example, if the default location is something other than "/tmp", it might not exist during "make check".) When checking an already-running old postmaster, find out its actual socket directory location from postmaster.pid, if possible. This dodges problems with an old postmaster having a configured location different from the default built into pg_upgrade's libpq. We can't find that out if the old postmaster is pre-9.1, so also document how to cope with such scenarios manually. In support of this, centralize handling of the connection-related command line options passed to pg_upgrade's subsidiary programs, such as pg_dump. This should make future changes easier. Bruce Momjian and Tom Lane
* In pg_upgade, document that the port numbers must be different whenBruce Momjian2012-08-311-2/+4
| | | | checking an old running server.
* Document that the pg_upgrade user of rsync might want to skip someBruce Momjian2012-07-261-1/+3
| | | | | | files, like postmaster.pid. Backpatch to 9.2.
* Document that Log-Shipping Standby Servers cannot be upgraded byBruce Momjian2012-07-101-0/+6
| | | | | | pg_upgrade. Backpatch to 9.2.
* Put back word that was mysteriously lost in man page conversionPeter Eisentraut2012-05-191-1/+1
|
* Fix a whitespace issue with the man pagesPeter Eisentraut2012-05-151-4/+2
| | | | | See 6ef24487967692604b07a4a54e71821a60fb729a for an explanation. This is the same for the new man pages.
* Remove whitespace from end of linesPeter Eisentraut2012-05-151-1/+1
| | | | pgindent and perltidy should clean up the rest.
* Split contrib documentation into extensions and programsPeter Eisentraut2012-05-091-60/+97
| | | | | | | Create separate appendixes for contrib extensions and other server plugins on the one hand, and utility programs on the other. Recast the documentation of the latter as refentries, so that man pages are generated.
* In pg_upgrade, add various logging improvements:Bruce Momjian2012-03-121-19/+8
| | | | | | | | | | | add ability to control permissions of created files have psql echo its queries for easier debugging output four separate log files, and delete them on success add -r/--retain option to keep log files after success make logs file append-only remove -g/-G/-l logging options sugggest tailing appropriate log file on failure enhance -v/--verbose behavior
* In pg_upgrade, only lock the old cluster if link mode is used, and do itBruce Momjian2012-03-051-16/+13
| | | | | | | right after we restore the schema (a common failure point), and right before we do the link operation. Per suggesgtions from Robert and ^!C^!^@lvaro
* Improve wording of pg_upgrade logfile option:Bruce Momjian2012-02-221-1/+1
| | | | -l, --logfile=FILENAME log internal activity to file\n\
* In pg_upgrade, allow tables using regclass to be upgraded because weBruce Momjian2011-12-051-1/+1
| | | | preserve pg_class oids since PG 9.0.
* In pg_upgrade, add -o/-O options to pass parameters to the servers, andBruce Momjian2011-10-101-0/+22
| | | | document its use for config-only directory installs.
* Move pg_upgrade doc mention of the port numbers to the same place.Bruce Momjian2011-10-061-3/+3
|
* In pg_upgrade, disallow migration of 8.3 clusters using contrib/ltreeBruce Momjian2011-09-071-0/+5
| | | | | | | | because its internal format was changed in 8.4. Backpatch to 9.0 and 9.1. Report by depesz, diagnosis by Tom.
* Remove whitespace from end of linesPeter Eisentraut2011-08-071-1/+1
|
* In the pg_upgrade docs, move 50432 port mention to the place where weBruce Momjian2011-07-011-5/+5
| | | | talk about client access.
* Change pg_upgrade to use port 50432 by default to avoid unintendedBruce Momjian2011-07-011-11/+15
| | | | | client connections during the upgrade. Also rename data/bin/port environment variables to being with 'PG'. Also no longer honor PGPORT.
* In pg_upgrade docs, clarify that link mode uses "hard" links.Bruce Momjian2011-06-231-8/+12
| | | | Backpatch to 9.1 and 9.0.
* In pg_upgrade, document that link mode has to have data directories onBruce Momjian2011-06-141-4/+7
| | | | | | | | | the same file system, and that authentication should lock out normal users. Per suggestsion from #postgresql irc channel. Backpatch to 9.1.
* Allow pg_upgrade to honor libpq environment variables. Add 'local'Bruce Momjian2011-05-161-19/+26
| | | | checks for PGHOST and PGHOSTADDR.
View Lorry Controller Status