From: Alexander Lakhin <exclusion@gmail.com>
To: Robins Tharakan <tharakan@gmail.com>
To: Richard Guo <guofenglinux@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org, Heikki Linnakangas <hlinnaka@iki.fi>
Cc: Álvaro Herrera <alvherre@alvh.no-ip.org>
Subject: Re: BUG #18832: Segfault in GrantLockLocal
Date: Fri, 28 Mar 2025 08:00:00 +0200
Message-ID: <49f79a5e-9570-445b-b454-c07efd78725e@gmail.com> (raw)
In-Reply-To: <CAEP4nAwBJqCGfrm2B92KS6UkMs5g+JEFBTcnrM3zY2DiM1Cw4Q@mail.gmail.com>
References: <CAMbWs4-+mmAsNM=ewbYWTKSkpXDGuj_toeEO=sKwa4YGaqfD=w@mail.gmail.com>
<202503071037.nrgp6vmhflcl@alvherre.pgsql>
<CAEP4nAwBJqCGfrm2B92KS6UkMs5g+JEFBTcnrM3zY2DiM1Cw4Q@mail.gmail.com>
Hello Robins and Richard,
27.03.2025 11:42, Robins Tharakan wrote:
> Core was generated by `postgres: 44fe6ceb51f@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)
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: pgsql-bugs@postgresql.org
Cc: exclusion@gmail.com, tharakan@gmail.com, guofenglinux@gmail.com, hlinnaka@iki.fi, alvherre@alvh.no-ip.org
Subject: Re: BUG #18832: Segfault in GrantLockLocal
In-Reply-To: <49f79a5e-9570-445b-b454-c07efd78725e@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox