| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: XLog changes for 9.3 |
| Date: | 2012-06-13 03:16:09 |
| Message-ID: | 20120613031609.GA14881@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jun 07, 2012 at 02:52:04PM -0400, Tom Lane wrote:
> > So you can pretty much kiss goodbye to the idea of pg_upgrade.
>
> And that is certainly nonsense. I don't think pg_upgrade even knows
> about this, and if it does we can surely fix it.
pg_upgrade doesn't know anything about xlog files --- all its interaction
in that area is through pg_resetxlog and it doesn't look at the xlog
details.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2012-06-13 04:07:36 | Re: WIP patch for Todo Item : Provide fallback_application_name in contrib/pgbench, oid2name, and dblink |
| Previous Message | Vlad Arkhipov | 2012-06-13 02:59:10 | COMMENT on function's arguments |