| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, PostgreSQL-documentation <docs(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] INSTALL/install.sgml file |
| Date: | 2000-06-05 15:37:43 |
| Message-ID: | 12133.960219463@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> In looking at the INSTALL/install.sgml files, I see that there are no
> instructions for removing the /data directory after the backup, so
> initdb will succeed. Should that be suggested after the backup is
> performed? If not, initdb will fail. Also, I have to add something to
> the initdb step to tell 7.* users they don't need initdb.
What? It says "move the old directories out of the way" at the bottom
of step 6.
Possibly that should be promoted into a whole separate step, rather than
being just an afterthought to killing the postmaster.
This step and step 11 should also mention pg_upgrade as a possible
alternative to doing a full reload. (But encourage people to make
the backup anyway ;-).)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2000-06-05 17:05:02 | Re: [HACKERS] INSTALL/install.sgml file |
| Previous Message | Bruce Momjian | 2000-06-05 10:58:27 | INSTALL/install.sgml file |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-06-05 15:44:46 | Re: AW: New warning code for missing FROM relations |
| Previous Message | Kevin Lo | 2000-06-05 15:12:58 | Re: [HACKERS] pg on NT |