public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: James Creasy <[email protected]>
Cc: [email protected]
Subject: Re: Hello, novice Postgres user, seg fault investigation
Date: Wed, 24 Apr 2024 17:59:01 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CADN1ADcgWN+kWEeCmQ4pwx91PjAXjYuYYunSArw9cyvDW8ZeZg@mail.gmail.com>
References: <CADN1ADcgWN+kWEeCmQ4pwx91PjAXjYuYYunSArw9cyvDW8ZeZg@mail.gmail.com>

James Creasy <[email protected]> writes:
> Now the interesting part, we're getting a seg fault which goes away when we
> run VACUUM on the table before writing to it, which is perplexing as the
> table can be newly created and contains a few hundred rows. How could the
> db get into a fatal state so quickly?

If you didn't find it already, there's some advice here:

https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend

With so many moving parts, it's hard to guess whether the bug is in
Postgres or PostGIS or what, but a stack trace should be informative.

Also, as that page mentions, it's a good idea to make sure you
are on latest release(s) before you spend time digging.

			regards, tom lane

view thread (3+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Hello, novice Postgres user, seg fault investigation
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox