| From: | "Markus Bertheau" <mbertheau(dot)pg(at)googlemail(dot)com> |
|---|---|
| To: | "Tena Sakai" <tsakai(at)gallo(dot)ucsf(dot)edu> |
| Cc: | "Peter Childs" <peterachilds(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: 8.3.0 upgrade, confused by documentation |
| Date: | 2008-02-13 16:57:16 |
| Message-ID: | 684362e10802130857g48dead64u5dceb14cd1ebbf88@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
2008/2/13, Tena Sakai <tsakai(at)gallo(dot)ucsf(dot)edu>:
> b) keep the 8.2.4 up and running, but via pg_hab.conf
> make sure nobody can use the database.
That's basically up to you, you can leave it open. The backup will be
consistent, but it won't contain any changes made to the database
after pg_dumpall has been started.
> c) as user postgres, while environmental variables
> PGHOST and PGPORT is set correctly, execute the
> unix command below:
> (path_to_8.3.0)/pg_dumpall > data_saved
> Where I am fuzzy is step c). Ie., can I execute 8.3.0
> program (pg_dumpall) without running 8.3.0 postgreSQL?
> And will it produce what I want?
Yes, you can. It will connect to the 8.2.4 version.
Markus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Shapiro | 2008-02-13 17:27:16 | CONTEXT messages for raise EXCEPTION |
| Previous Message | David Wall | 2008-02-13 05:36:36 | Re: warm database. |