MIME-Version: 1.0
References: <CAM-5MT0B3RUXdWmzeK4DYF_igUKqViYS22pQoMr7pANrLHDVKg@mail.gmail.com>
In-Reply-To: <CAM-5MT0B3RUXdWmzeK4DYF_igUKqViYS22pQoMr7pANrLHDVKg@mail.gmail.com>
From: Igor Korot <ikorot01@gmail.com>
Date: Thu, 24 Oct 2024 11:12:09 -0500
Message-ID: <CA+FnnTyjKTeo+8PMVMTZSzsrGFUHK57+8bAPT6LVpKME03SR1A@mail.gmail.com>
Subject: Re: Assistance Required: Timeout or Buffer Overflow Issue in
 PostgreSQL Client Application
To: Sasmit Utkarsh <utkarshsasmit@gmail.com>
Cc: pgsql-general <pgsql-general@postgresql.org>, pgsql-general@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CA%2BFnnTyjKTeo%2B8PMVMTZSzsrGFUHK57%2B8bAPT6LVpKME03SR1A%40mail.gmail.com>
Precedence: bulk

Hi,
Is this a complete backtrace?
Can you post a complete backtrace? We need to see if there is a reference
to your application code?

What language is it written in?
What operation this thread was performing?

Thank you.

On Thu, Oct 24, 2024 at 11:12=E2=80=AFAM Sasmit Utkarsh <utkarshsasmit@gmai=
l.com> wrote:
>
> Dear PostgreSQL Community Team,
>
> I hope this message finds you well. I am reaching out for assistance with=
 an issue encountered in our application, which communicates with PostgreSQ=
L using the libpq client library.
>
> Issue Details:
> We have observed a problem where one of the application's threads gets st=
uck during a database operation. Below is a stack trace of the affected thr=
ead:
>
> Application Logs:
> Oct 23 10:08:44.806235 cucmtpccu1 shc-server@2.service[966034]: 0966070{e=
f5f81a7-d35b-4604-953d-a35665e505b7.010000}KIP8-SQL_get_tpf_rw()-SQL read d=
ata from File Address before lock fa(-1810606079) fa(94145801) fa2 htonl(22=
549652)
> Oct 23 10:08:44.806235 cucmtpccu1 shc-server@2.service[966034]: 0966070{e=
f5f81a7-d35b-4604-953d-a35665e505b7.010000}KIP8-SQL_get_tpf_rw() SelectData=
Command =3D CALL SQL_select_data_procedure($1, $2, NULL, NULL) hold(0) fa(-=
1810606079)
> Oct 23 10:08:44.807814 cucmtpccu1 shc-server@2.service[966034]: *** buffe=
r overflow detected ***: terminated
>
> Stack Trace of Thread 966070:
> #0  0x00000000f7ee1129 __kernel_vsyscall (linux-gate.so.1)
> #1  0x00000000f6ba23b7 __poll (libc.so.6)
> #2  0x00000000f792e5b5 __interceptor_poll (libasan.so.8)
> #3  0x00000000f72b30a8 pqSocketCheck (libpq.so.5)
> #4  0x00000000f72b3864 pqWaitTimed (libpq.so.5)
> #5  0x00000000f72b38d2 pqWait (libpq.so.5)
> #6  0x00000000f72aff03 PQgetResult (libpq.so.5)
> #7  0x00000000f72b036a PQexecFinish (libpq.so.5)
> #8  0x0000000008106dd4 checkLOCK (server)
> #9  0x000000000811d871 SQL_get_tpf_rw (server)
> ...
>
> The stack trace shows that the thread is stuck in a poll operation while =
waiting for socket activity within the PostgreSQL client library (libpq). W=
e suspect this could be related to a network timeout or issue. However, the=
 application logs indicate a buffer overflow before the crash, which raises=
 questions about whether these are related.
>
> Questions:
> -Could the buffer overflow be causing the crash, and if so, how is it rel=
ated to the socket activity?
> -Are there specific configurations or checks we should perform to diagnos=
e this issue further?
> -Any suggestions for possible solutions to resolve this problem?
>
> For additional context, I've verified that the specified record does exis=
t in the database, and I am also attaching the implementation details for t=
he checkLOCK function corresponding to the stack trace.
>
> Please let me know if you need any more details
>
> Your assistance with troubleshooting this would be highly appreciated.
>
> Regards,
> Sasmit Utkarsh
> +91-7674022625