| From: | "Stephen R(dot) van den Berg" <srb(at)cuci(dot)nl> |
|---|---|
| To: | Florian Pflug <fgp(at)phlo(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Success (Re: page 1 of relation global/11787 was uninitialized) |
| Date: | 2013-04-09 19:34:32 |
| Message-ID: | 20130409193432.GA1481@cuci.nl |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Florian Pflug wrote:
>> I used this to upgrade to 9.0.13, which indeed is fully compatible with
>> Debian. It started up like a charm. I can upgrade it to 9.1.9 now
>> (while I'm at it).
>Since you've been running with full_page_writes=off, I suggest you update
>to 9.1 by dumping and reloading your data (i.e. pg_dumpall) instead of
>via binary upgrades (i.e. pg_upgrade).
I need to do that anyway, since the pg_upgradecluster script of Debian
(or is it a native PostgreSQL script?) does not support tablespaces.
>That way, you can be sure that your data is consistent (from postgres'
>POV anyway) after the upgrade. pg_upgrade OTOH will only notice
>inconsistencies in the system tables, since the data files of user tables
>and indices are simply copied unchanged.
Good point. Thanks.
--
Stephen.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2013-04-09 19:43:30 | Re: [COMMITTERS] pgsql: Add sql_drop event for event triggers |
| Previous Message | Kevin Grittner | 2013-04-09 18:17:21 | Re: MV patch broke users of ExplainOneQuery_hook |