| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: -Wformat-zero-length |
| Date: | 2012-08-08 20:23:04 |
| Message-ID: | CA+TgmoY_5xkG3+q5OFDmmL1WFhGhNfBxq7xNVi=bPYT86=2i_w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Aug 7, 2012 at 10:59 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Yes, the list of rough edges is the 14-steps you have to perform to run
> pg_upgrade, as documented in the pg_upgrade manual page:
>
> http://www.postgresql.org/docs/9.2/static/pgupgrade.html
>
> The unknown is how to reduce the number of steps in a way the community
> would find acceptable.
I think this is one good idea:
http://archives.postgresql.org/message-id/29806.1340655654@sss.pgh.pa.us
The number of steps is an issue, but the likelihood of the actual
pg_upgrade run failing or doing the wrong thing is also something we
need to work on.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2012-08-08 20:44:52 | Re: Statistics and selectivity estimation for ranges |
| Previous Message | Simon Riggs | 2012-08-08 19:54:23 | Re: Inserting heap tuples in bulk in COPY |