From: Tom Lane <tgl@sss.pgh.pa.us>
To: abbas alizadeh <ramkly@yahoo.com>
cc: pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Segmentation fault
In-reply-to: <468712F9-7F36-4AEA-B8A4-1007837D4B3E@yahoo.com>
References: <468712F9-7F36-4AEA-B8A4-1007837D4B3E.ref@yahoo.com>
 <468712F9-7F36-4AEA-B8A4-1007837D4B3E@yahoo.com>
Comments: In-reply-to abbas alizadeh <ramkly@yahoo.com>
	message dated "Tue, 26 Jul 2022 17:51:05 +0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <2356859.1658850043.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Tue, 26 Jul 2022 11:40:43 -0400
Message-ID: <2356860.1658850043@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2356860.1658850043%40sss.pgh.pa.us>
Precedence: bulk

abbas alizadeh <ramkly@yahoo.com> writes:
> I got =E2=80=9Cterminated by signal 11, segmentation falt=E2=80=9D error=
 in my database. =

> I=E2=80=99m using pg v13.7
> Query causing that error: =E2=80=9Cset client_encoding=3D utf-8=E2=80=9D

Hmm, that is pretty well-tested code.

> There is no core file in data folder.

Maybe you are starting the server under "ulimit -c 0"?  See also
the advice at

https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_=
backend

> Any idea how can I find the root case for this error?

With only this amount of information, there's not much to be done.
If you could get a stack trace maybe we'd have some ideas.

			regards, tom lane