On Fri, 8 Nov 2024 at 17:11, Alvaro Herrera wrote:
>
> We recently had a customer report a very strange problem, involving a
> very large insert-only table: without explanation, insertions would
> stall for several seconds, causing application timeout and process
> accumulation and other nastiness
Michael Paquier writes:
> On Tue, Aug 07, 2018 at 12:19:13PM -0400, Alvaro Herrera wrote:
>> Now that the minors have been tagged, I'm considering pushing this
>> shortly to 9.6 - master.
> I may be missing something, but the next round of minor releases is not
> tagged yet, and only stamped. So
On Tue, Aug 07, 2018 at 12:19:13PM -0400, Alvaro Herrera wrote:
> Now that the minors have been tagged, I'm considering pushing this
> shortly to 9.6 - master.
I may be missing something, but the next round of minor releases is not
tagged yet, and only stamped. So I think that you should hold on
On 2018-Aug-02, Alvaro Herrera wrote:
> After considering several possible solutions, I propose to have
> heap_xlog_visible compute free space for any page being marked frozen;
> Pavan adds to that to have heap_xlog_clean compute free space for all
> pages also. This means that if we later promot
We recently had a customer report a very strange problem, involving a
very large insert-only table: without explanation, insertions would
stall for several seconds, causing application timeout and process
accumulation and other nastiness.
After some investigation, we narrowed this down to happenin
