On Mon, Jul 16, 2012 at 02:27:45PM +0930, Stephen Davies wrote:
> (I used the rsync method suggested in the last paragraph of the pg_upgrade
> man
> pages to create a copy of the databases to be upgraded.
> This works fine except that the paragraph should also point out that the file
> postmaster.pid must be deleted from the copy to avoid an error message from
> pg_upgrade.)
OK, we already document the problems with postmaster.pid and rsync in
the backup section, so I added a mention of that to the pg_upgrade docs,
and backpatched that to 9.2.
--
Bruce Momjian <[email protected]> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml
new file mode 100644
index cffcebb..fcbe551
*** a/doc/src/sgml/pgupgrade.sgml
--- b/doc/src/sgml/pgupgrade.sgml
*************** psql --username postgres --file script.s
*** 530,536 ****
of the old cluster, use <command>rsync</> to create a dirty
copy of the old cluster while the server is running, then shut down
the old server and run <command>rsync</> again to update the copy with any
! changes to make it consistent.
</para>
<refsect2>
--- 530,538 ----
of the old cluster, use <command>rsync</> to create a dirty
copy of the old cluster while the server is running, then shut down
the old server and run <command>rsync</> again to update the copy with any
! changes to make it consistent. You might want to exclude some
! files, e.g. <filename>postmaster.pid</>, as documented in <xref
! linkend="backup-lowlevel-base-backup">.
</para>
<refsect2>
--
Sent via pgsql-admin mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
