| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us> |
| Subject: | Re: pg_upgrade and toasted pg_largeobject |
| Date: | 2016-05-03 17:58:39 |
| Message-ID: | CA+TgmoahT=oT7V6ooML+Phs=9ApqiTeoFQ5hPWrDkwNGtErhSQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, May 3, 2016 at 1:38 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Any thoughts what to do with this? We could decide that it's a bug fix
> and backpatch, or decide that it's a new feature and delay till 9.7,
> or decide that it's a minor bug fix and add it to 9.6 only. I kinda lean
> towards the last alternative.
I'm fine with that.
(But I haven't reviewed the code.)
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2016-05-03 18:06:58 | Re: Timeline following for logical slots |
| Previous Message | Tom Lane | 2016-05-03 17:58:36 | Re: ALTER TABLE lock downgrades have broken pg_upgrade |