postgres got segmentation fault occasionally when postgrest reload config about postgrest HOT 4 CLOSED

I'd suggest to report an issue against timescaledb instead, because database server should not segfault, period.

from postgrest.

Interesting that there are two reports of this happening now with #3138 and this. Once it's the pgpro fork and once with the timescaledb extension - although other factors could play into this as well.

@LaurenceChau are you running stock postgres 16.1 or any fork? Are you using any other extensions or just timescaledb?

from postgrest.

Interesting that there are two reports of this happening now with #3138 and this. Once it's the pgpro fork and once with the timescaledb extension - although other factors could play into this as well.

@LaurenceChau are you running stock Postgres 16.1 or any fork? Are you using any other extensions or just timescaledb?

The problem can be fixed by truncating timescaledb hypertable. Not sure if it is related to synchronous_commit, disabled it before.

I am running postgreSQL16.1 and using timescaledb extensions only. Try to enable debug log and turn on synchronous_commit if I can get more findings.

When Segfault occurred, connecting through a psql client would not cause any problem, however connect through postrest will cause the segfault again. I guess a new postgrest connection may trigger a db bug?

from postgrest.

Interesting that there are two reports of this happening now with #3138 and this. Once it's the pgpro fork and once with the timescaledb extension - although other factors could play into this as well.
@LaurenceChau are you running stock Postgres 16.1 or any fork? Are you using any other extensions or just timescaledb?

The problem can be fixed by truncating timescaledb hypertable. Not sure if it is related to synchronous_commit, disabled it before.

I am running postgreSQL16.1 and using timescaledb extensions only. Try to enable debug log and turn on synchronous_commit if I can get more findings.

When Segfault occurred, connecting through a psql client would not cause any problem, however connect through postrest will cause the segfault again. I guess a new postgrest connection may trigger a db bug?

Upgraded to timescaledb 2.13.1. It looks like the error has gone.

from postgrest.