Re: BUG #18612: Postgres crash with segfault on disk full - ____strtof_l_internal (strtod_l.c:1019)

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: bhavin(dot)ec50(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18612: Postgres crash with segfault on disk full - ____strtof_l_internal (strtod_l.c:1019)
Date: 2024-09-12 10:04:51
Message-ID: 25027F1F-B290-4654-9B90-B7DA7F97B8BE@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On 12 Sep 2024, at 09:19, PG Bug reporting form <noreply(at)postgresql(dot)org> wrote:

> I have observed Postgres coredump upon disk full. Below is the stack trace
> of core dump.

> I have another version of Postgres 9.2 and haven't observed same on it.
> Please take a look and let me know if require more details.

PostgreSQL doesn't cope all that well when disk is full, and I can imagine it
crashing at a number of different places even with the same version (let alone
one which shipped 12 years ago).

--
Daniel Gustafsson

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2024-09-12 10:35:30 BUG #18615: installer cannot be executed as "nt-autorität\system"
Previous Message PG Bug reporting form 2024-09-12 08:54:42 BUG #18614: [ECPG] out of bound in DecodeDateTime