Re: reindexdb & clusterdb broken against pre-7.3 servers

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Julien Rouhaud <rjuju123(at)gmail(dot)com>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, noah(at)leadboat(dot)com
Subject: Re: reindexdb & clusterdb broken against pre-7.3 servers
Date: 2019-05-07 03:24:31
Message-ID: 28120.1557199471@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Michael Paquier <michael(at)paquier(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2019-05-07 03:25:43 Re: Heap lock levels for REINDEX INDEX CONCURRENTLY not quite right?
Previous Message Tom Lane 2019-05-07 03:18:28 Re: accounting for memory used for BufFile during hash joins