From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Peter Smith <smithpb2250(at)gmail(dot)com> |
Cc: | David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: What is lurking in the shadows? |
Date: | 2021-05-18 02:25:37 |
Message-ID: | YKMloRln/dRM92fO@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, May 18, 2021 at 12:08:57PM +1000, Peter Smith wrote:
> Yeah, I would like to work my way through all of these warnings in my
> spare time and report back to this thread (after 1-2 months?) with a
> detailed analysis.
The next commit fest is at the beginning of July, so there are a
couple of weeks of margin here.
> After that it should become much clearer what / if any action should
> be taken next.
If you can dive into the details, that would be nice! My take would
be to look first at the local-local conflicts and rename all the
variables that conflict so as any backpatch done in the areas changed
cause a compilation failure. Some of the global-local conflicts are
simple enough to solve, these could go second. Each of them requires
a case-by-case lookup, of course.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2021-05-18 02:26:34 | Re: What is lurking in the shadows? |
Previous Message | Michael Paquier | 2021-05-18 02:20:49 | Re: Addition of authenticated ID to pg_stat_activity |