as of subject, it should be 16.3.
scenario was:
- a few months ago install + deployed user data pg 16.2.
- 2 days ago, updated to 16.3
now I can reproduce the issue, the segment fault comes from
postgres[495645]: segfault at 0 ip 7f318b17e1f4 sp 7ffc7f1b15d8
error 4 in citus.so[7f318b0a40
On Mon, 20 May 2024 at 22:32, milist ujang wrote:
>
> postgres 16.1; rocky 9.3
>
> when connect to database postgres this query is OK, but run on user database,
> got segmentation fault.
I tried your query on 16.1 and I'm unable to reproduce the crash.
Are you able to recreate this on a freshly
postgres 16.1; rocky 9.3
when connect to database postgres this query is OK, but run on user
database, got segmentation fault.
2024-05-20 17:16:54.942 WIB,,,134291,,6648420a.20c93,165,,2024-05-18
12:52:10 WIB,,0,LOG,0,"server process (PID 487952) was terminated by
signal 11: Segmentation fau
