| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| 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>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: format of pg_upgrade loadable_libraries warning |
| Date: | 2019-11-28 08:58:06 |
| Message-ID: | 77211DCD-1C76-4B91-BCB5-FE95C328A0DB@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 28 Nov 2019, at 02:26, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> I have applied the patch, with improved wording. I only applied this to
> PG 13 since I was worried old tools might be checking for the old error
> text. Should this be backpatched more?
I don't think it's unreasonable to assume that there are lots of inhouse
tooling for pg_upgrade orchestration which grep for specific messages.
Stopping at 13 seems perfectly reasonable for this change.
cheers ./daniel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2019-11-28 09:01:18 | Re: [Incident report]Backend process crashed when executing 2pc transaction |
| Previous Message | Yugo Nagata | 2019-11-28 08:10:52 | Re: Implementing Incremental View Maintenance |