Re: slow get_actual_variable_range with long running transactions - Mailing list pgsql-hackers

From Marc Cousin
Subject Re: slow get_actual_variable_range with long running transactions
Date
Msg-id 42efd5ff-aa9d-0ff9-58b8-f7d5ddeb5468@gmail.com
Whole thread Raw
In response to Re: slow get_actual_variable_range with long running transactions  (Marc Cousin <cousinmarc@gmail.com>)
List pgsql-hackers
On 16/06/2020 18:28, Marc Cousin wrote:
> Oh, sorry about that, I forgot to detail this. I tested on both 10.13 (which is the production environment on which
wefaced this), and on 12.3, with the same problem. 
>
> On 16/06/2020 17:51, Tom Lane wrote:
>> Marc Cousin <cousinmarc@gmail.com> writes:
>>> Of course, what happens here is that the histogram says that max(a) is 1000000, and get_actual_variable_range
verifiesthe real upper bound. And has to read quite a few dead index records. 
>>
>> We've revised that logic several times to reduce the scope of the
>> problem.  Since you didn't say which PG version you're using exactly,
>> it's hard to offer any concrete suggestions.  But I fear there's
>> not a lot you can do about it, other than upgrading if you're on a
>> pre-v11 release.
>>
>>             regards, tom lane
>>
>
As you told me this I did some more tests on PG 12.

The first attempt is the same (maybe some hints being set or something like that), the second is much faster. So
nothingto see here, sorry for the noise. 

And sorry for the previous top posting :)

Regards


Attachment

pgsql-hackers by date:

Previous
From: Marc Cousin
Date:
Subject: Re: slow get_actual_variable_range with long running transactions
Next
From: Bruce Momjian
Date:
Subject: Re: language cleanups in code and docs