Re: BUG #17254: Crash with 0xC0000409 in pg_stat_statements when pg_stat_tmp\pgss_query_texts.stat exceeded 2GB.

From: Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: egashira(dot)yusuke(at)fujitsu(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #17254: Crash with 0xC0000409 in pg_stat_statements when pg_stat_tmp\pgss_query_texts.stat exceeded 2GB.
Date: 2021-10-31 23:34:15
Message-ID: CAC+AXB3L3pB-SGqrLBiXqg9yQZDNURGgyT63QRAnZ=o_oUb9-A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sun, Oct 31, 2021 at 6:07 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

>
> Here's a quick patch for that. I don't have any ability to check it
> on Windows, but the logic is easy to verify by reducing the arbitrary
> constant to something small. (I used 1GB, not INT_MAX, because I figured
> we ought to read in multiples of a filesystem block if possible.)
>
> I have tested the patch in Windows and it works as expected.

Regards,

Juan José Santamaría Flecha

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Geoghegan 2021-11-01 00:19:29 Re: BUG #17245: Index corruption involving deduplicated entries
Previous Message Tom Lane 2021-10-31 22:46:34 Re: BUG #17254: Crash with 0xC0000409 in pg_stat_statements when pg_stat_tmp\pgss_query_texts.stat exceeded 2GB.