public inbox for [email protected]  

help / color / mirror / Atom feed

From: TIM CHILD <[email protected]>
To: [email protected]
Subject: Re: Hello, novice Postgres user, seg fault investigation
Date: Wed, 24 Apr 2024 15:08:36 -0700 (PDT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <CADN1ADcgWN+kWEeCmQ4pwx91PjAXjYuYYunSArw9cyvDW8ZeZg@mail.gmail.com>
References: <CADN1ADcgWN+kWEeCmQ4pwx91PjAXjYuYYunSArw9cyvDW8ZeZg@mail.gmail.com>

James,
 
One of the effects of VACUUM is to update  table statistics. This provides information that  allows  query planner to better optimize your queries.  So assuming there is residual data already in the table before writing to it,  the  VACUUM that updated statistics may of changed your query plans. 
 
While the possibility of  changed query plans in no way explains the seg fault.  It may explain the change in behavior   the pre/post VACUUM.
 
In general without seeing more information regarding table structure, queries, table  indices,  query plans (pre/post) my answer is pure speculation.  It would also be beneficial to know what platform and version of Postgres, PostgREST and PostGIS you are running?
 
-Tim

> On 04/24/2024 2:26 PM PDT James Creasy <[email protected]> wrote:
>  
>  
> Hi,
>  
> Trying to figure out which list to post which types of questions to. New to Postgres and the community so I thought I'd post an introduction. 
>  
> We're also using the PostGIS extension for 3D data, PostgREST for the API, socketio for push notifications. Deployed on AWS via Docker. We analyze 3D data with incremental changes over year+ long time periods.  
>  
> 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? 
>  
> We are setting up Postgres for debugging and see where we go from there. Looks like gdb and valgrind are still the tools of choice. Lots to learn, and that's where we are currently. 
>  
> James 
> Bay Area, U.S.A
> 

view thread (3+ messages)

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]
  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