Re: reindexdb & clusterdb broken against pre-7.3 servers
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: Julien Rouhaud <rjuju123@gmail.com>,
Andrew Dunstan <andrew.dunstan@2ndquadrant.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
noah@leadboat.com
Date: 2019-05-07T03:24:31Z
Lists: pgsql-hackers
Michael Paquier <michael@paquier.xyz> writes: > On Mon, May 06, 2019 at 10:23:07PM -0400, Tom Lane wrote: >> The originally-complained-of breakage exists in all active branches, >> so is it really OK to commit this only in HEAD? > I did not think that it would be that critical for back-branches, but > I don't mind going ahead and remove the code there as well. Are there > any objections with it? > Also, wouldn't we want instead to apply on back-branches the first > patch proposed on this thread which fixes the query generation for > this pre-7.3 related code? Given that we pushed out the bad code a year ago and nobody's complained, I think it's safe to assume that no one is using any supported release with a pre-7.3 server. It's reasonable to doubt that this is the only problem the affected applications would have with such a server, too. I don't see a lot of point in "fixing" this code unless somebody actually tests that. regards, tom lane
Commits
-
Remove some code related to 7.3 and older servers from tools of src/bin/
- 9a6a1042ab40 9.4.23 landed
- 6de005121c48 9.5.18 landed
- b806618ccf8c 9.6.14 landed
- 6bd3203b9e54 10.9 landed
- 64ad372346b3 11.4 landed
- af82f95abb23 12.0 landed