From: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
---|---|
To: | Robins Tharakan <tharakan(at)gmail(dot)com>, Richard Guo <guofenglinux(at)gmail(dot)com> |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Subject: | Re: BUG #18832: Segfault in GrantLockLocal |
Date: | 2025-03-28 06:00:00 |
Message-ID: | 49f79a5e-9570-445b-b454-c07efd78725e@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hello Robins and Richard,
27.03.2025 11:42, Robins Tharakan wrote:
> Core was generated by `postgres: 44fe6ceb51f(at)sqith: u8 postgres 127.0.0.1(37802) ROLLBACK '.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0 0x00005fbb793422d6 in GrantLockLocal (locallock=0x5fbba9c35c38, owner=0x5fbba9b419d8) at lock.c:1805
> 1805 lockOwners[i].owner = owner;
> (gdb) bt
> #0 0x00005fbb793422d6 in GrantLockLocal (locallock=0x5fbba9c35c38, owner=0x5fbba9b419d8) at lock.c:1805
> #1 0x00005fbb79342546 in GrantAwaitedLock () at lock.c:1887
> #2 0x00005fbb7935654e in LockErrorCleanup () at proc.c:814
> #3 0x00005fbb78e54fb2 in AbortTransaction () at xact.c:2853
> #4 0x00005fbb78e55781 in CommitTransactionCommandInternal () at xact.c:3275
> #5 0x00005fbb78e555f0 in CommitTransactionCommand () at xact.c:3163
> #6 0x00005fbb7936a05c in finish_xact_command () at postgres.c:2834
> #7 0x00005fbb7936744e in exec_simple_query (query_string=0x5fbba9b030b0 "ROLLBACK;") at postgres.c:1298
> #8 0x00005fbb7936cbf3 in PostgresMain (dbname=0x5fbba9b44258 "postgres", username=0x5fbba9b44240 "u8") at postgres.c:4757
> #9 0x00005fbb79362779 in BackendMain (startup_data=0x7ffc6f57c3e0, startup_data_len=24) at backend_startup.c:122
> #10 0x00005fbb79265e5a in postmaster_child_launch (child_type=B_BACKEND, child_slot=299, startup_data=0x7ffc6f57c3e0,
> startup_data_len=24, client_sock=0x7ffc6f57c440)
> at launch_backend.c:291
> #11 0x00005fbb7926c9fa in BackendStartup (client_sock=0x7ffc6f57c440) at postmaster.c:3580
> #12 0x00005fbb79269e14 in ServerLoop () at postmaster.c:1701
> #13 0x00005fbb7926970a in PostmasterMain (argc=3, argv=0x5fbba9abcab0) at postmaster.c:1399
> #14 0x00005fbb79108b07 in main (argc=3, argv=0x5fbba9abcab0) at main.c:230
Perhaps I observed the same issue:
https://www.postgresql.org/message-id/e11a30e5-c0d8-491d-8546-3a1b50c10ad4%40gmail.com
Best regards,
Alexander Lakhin
Neon (https://neon.tech)
From | Date | Subject | |
---|---|---|---|
Next Message | Tender Wang | 2025-03-28 16:39:58 | Re: BUG #18871: Cross-partition MERGE fails with unclear internal error |
Previous Message | PG Bug reporting form | 2025-03-28 05:00:01 | BUG #18871: Cross-partition MERGE fails with unclear internal error |