| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andreas Joseph Krogh <andreas(at)visena(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Release Note changes |
| Date: | 2017-09-04 12:30:18 |
| Message-ID: | CANP8+jLeAww2N_YhoCY+yk81M7eAntdohN_4k_6+umO7EmE1Hw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4 September 2017 at 10:34, Andreas Joseph Krogh <andreas(at)visena(dot)com> wrote:
> I'd like at big red warning "Logical decoding doesn't support Large Objects"
> in that case;
>
> "If upgrading from a 9.4 server or later, and you don't use Large Objects,
> external utilities using logical decoding, such as pglogical or
> proprietary alternatives, can also provide an alternate route,
> often with lower downtime."
>
> pg_upgrade or pg_dump is really the only option for us using LOs.
Sounds like we could change that, or at least add a WARNING that there are LOs.
Patches welcome.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2017-09-04 12:31:32 | Re: WIP: long transactions on hot standby feedback replica / proof of concept |
| Previous Message | Rajkumar Raghuwanshi | 2017-09-04 12:30:13 | Re: advanced partition matching algorithm for partition-wise join |