Postgres Pro
Downloads
Home   >   mailing lists

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

From Juan José Santamaría Flecha
Subject Re: BUG #17254: Crash with 0xC0000409 in pg_stat_statements when pg_stat_tmp\pgss_query_texts.stat exceeded 2GB.
Date
Msg-id CAC+AXB3L3pB-SGqrLBiXqg9yQZDNURGgyT63QRAnZ=o_oUb9-A@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17254: Crash with 0xC0000409 in pg_stat_statements when pg_stat_tmp\pgss_query_texts.stat exceeded 2GB.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #17254: Crash with 0xC0000409 in pg_stat_statements when pg_stat_tmp\pgss_query_texts.stat exceeded 2GB.
List pgsql-bugs
Tree view

On Sun, Oct 31, 2021 at 6:07 PM Tom Lane <tgl@sss.pgh.pa.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

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #17254: Crash with 0xC0000409 in pg_stat_statements when pg_stat_tmp\pgss_query_texts.stat exceeded 2GB.
Next
From: Peter Geoghegan
Date:
Subject: Re: BUG #17245: Index corruption involving deduplicated entries