adnanhamdussalam opened a new issue, #1264:
URL: https://github.com/apache/cloudberry/issues/1264
Hi,
I am facing the issue regarding using pxf when I try to insert data from
external in the physical table I am facing the below error but when I execute
it with limit in the where condition it works:
psql (14.4, server 14.4)
Type "help" for help.
mydb=# insert into afiniti.test select * from myaf.ext_table where
time1>='2025-06-27' and time1<'2025-07-29';
WARNING: terminating connection because of crash of another server process
(seg5 10.1.1.1:50005 pid=475098)
DETAIL: The postmaster has commanded this server process to roll back the
current transaction and exit, because another server process exited abnormally
and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and
repeat your command.
WARNING: terminating connection because of crash of another server process
(seg3 10.1.1.1:50003 pid=475096)
DETAIL: The postmaster has commanded this server process to roll back the
current transaction and exit, because another server process exited abnormally
and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and
repeat your command.
WARNING: terminating connection because of crash of another server process
(seg7 10.1.1.1:50007 pid=475099)
DETAIL: The postmaster has commanded this server process to roll back the
current transaction and exit, because another server process exited abnormally
and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and
repeat your command.
WARNING: terminating connection because of crash of another server process
(seg6 10.1.1.1:50006 pid=475097)
DETAIL: The postmaster has commanded this server process to roll back the
current transaction and exit, because another server process exited abnormally
and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and
repeat your command.
WARNING: terminating connection because of crash of another server process
(seg1 10.1.1.1:50001 pid=475094)
DETAIL: The postmaster has commanded this server process to roll back the
current transaction and exit, because another server process exited abnormally
and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and
repeat your command.
WARNING: terminating connection because of crash of another server process
(seg0 10.1.1.1:50000 pid=475093)
DETAIL: The postmaster has commanded this server process to roll back the
current transaction and exit, because another server process exited abnormally
and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and
repeat your command.
WARNING: terminating connection because of crash of another server process
(seg2 10.1.1.1:50002 pid=475092)
DETAIL: The postmaster has commanded this server process to roll back the
current transaction and exit, because another server process exited abnormally
and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and
repeat your command.
WARNING: terminating connection because of crash of another server process
(seg4 10.1.1.1:50004 pid=475095)
DETAIL: The postmaster has commanded this server process to roll back the
current transaction and exit, because another server process exited abnormally
and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and
repeat your command.
ERROR: Error on receive from seg7 slice1 10.1.1.1:50007 pid=475115: server
closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
version
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
PostgreSQL 14.4 (Cloudberry Database 1.6.0 build 1) on x86_64-pc-linux-gnu,
compiled by gcc (GCC) 11.4.1 20231218 (Red Hat 11.4.1-3), 64-bit compiled on
Sep 3 2024 09:15:49
(1 row)
dmesg log output:
[Tue Jul 29 04:52:42 2025] postgres[476290]: segfault at 4400000043 ip
00007f0aa7252d88 sp 00007ffda3346750 error 4
[Tue Jul 29 04:52:42 2025] postgres[476292]: segfault at 4400000043 ip
00007f31369f5d88 sp 00007ffee61d4750 error 4
[Tue Jul 29 04:52:42 2025] postgres[476287]: segfault at 4400000043 ip
00007f3bb8593d88 sp 00007ffc2ac19750 error 4 in
libgcc_s-11-20240719.so.1[7f3bb8586000+13000] likely on CPU 3 (core 3, socket 0)
[Tue Jul 29 04:52:42 2025] Code: f1 ff ff 48 8b 44 24 08 49 89 84 24 a0 00
00 00 e9 36 fe ff ff 0f 1f 44 00 00 49 8b 94 24 98 00 00 00 49 8b 84 24 90 00
00 00 <80> 3a 48 0f 85 6f ff ff ff 48 b9 c7 c0 0f 00 00 00 0f 05 48 39 4a
[Tue Jul 29 04:52:42 2025] postgres[476286]: segfault at 4400000043 ip
00007fd63c5f5d88 sp 00007ffe5ee138d0 error 4
[Tue Jul 29 04:52:42 2025] in libgcc_s-11-20240719.so.1[7f31369e8000+13000]
likely on CPU 21 (core 9, socket 1)
[Tue Jul 29 04:52:42 2025] in libgcc_s-11-20240719.so.1[7f0aa7245000+13000]
[Tue Jul 29 04:52:42 2025] Code: f1 ff ff 48 8b 44 24 08 49 89 84 24 a0 00
00 00 e9 36 fe ff ff 0f 1f 44 00 00 49 8b 94 24 98 00 00 00 49 8b 84 24 90 00
00 00 <80> 3a 48 0f 85 6f ff ff ff 48 b9 c7 c0 0f 00 00 00 0f 05 48 39 4a
[Tue Jul 29 04:52:42 2025] likely on CPU 2 (core 2, socket 0)
[Tue Jul 29 04:52:42 2025] in libgcc_s-11-20240719.so.1[7fd63c5e8000+13000]
[Tue Jul 29 04:52:42 2025] Code: f1 ff ff 48 8b 44 24 08 49 89 84 24 a0 00
00 00 e9 36 fe ff ff 0f 1f 44 00 00 49 8b 94 24 98 00 00 00 49 8b 84 24 90 00
00 00 <80> 3a 48 0f 85 6f ff ff ff 48 b9 c7 c0 0f 00 00 00 0f 05 48 39 4a
[Tue Jul 29 04:52:42 2025] likely on CPU 41 (core 5, socket 3)
[Tue Jul 29 04:52:42 2025] Code: f1 ff ff 48 8b 44 24 08 49 89 84 24 a0 00
00 00 e9 36 fe ff ff 0f 1f 44 00 00 49 8b 94 24 98 00 00 00 49 8b 84 24 90 00
00 00 <80> 3a 48 0f 85 6f ff ff ff 48 b9 c7 c0 0f 00 00 00 0f 05 48 39 4a
[Tue Jul 29 04:52:42 2025] postgres[476291]: segfault at 4400000043 ip
00007fd6fe95bd88 sp 00007ffc70596150 error 4 in
libgcc_s-11-20240719.so.1[7fd6fe94e000+13000] likely on CPU 23 (core 11, socket
1)
[Tue Jul 29 04:52:42 2025] Code: f1 ff ff 48 8b 44 24 08 49 89 84 24 a0 00
00 00 e9 36 fe ff ff 0f 1f 44 00 00 49 8b 94 24 98 00 00 00 49 8b 84 24 90 00
00 00 <80> 3a 48 0f 85 6f ff ff ff 48 b9 c7 c0 0f 00 00 00 0f 05 48 39 4a
[Tue Jul 29 04:52:42 2025] postgres[476288]: segfault at 4400000043 ip
00007f750406cd88 sp 00007ffdebe71390 error 4 in
libgcc_s-11-20240719.so.1[7f750405f000+13000] likely on CPU 45 (core 9, socket
3)
[Tue Jul 29 04:52:42 2025] Code: f1 ff ff 48 8b 44 24 08 49 89 84 24 a0 00
00 00 e9 36 fe ff ff 0f 1f 44 00 00 49 8b 94 24 98 00 00 00 49 8b 84 24 90 00
00 00 <80> 3a 48 0f 85 6f ff ff ff 48 b9 c7 c0 0f 00 00 00 0f 05 48 39 4a
[Tue Jul 29 04:52:42 2025] postgres[476289]: segfault at 4400000043 ip
00007f331ebdbd88 sp 00007ffd6ddd2fd0 error 4 in
libgcc_s-11-20240719.so.1[7f331ebce000+13000] likely on CPU 8 (core 8, socket 0)
[Tue Jul 29 04:52:42 2025] Code: f1 ff ff 48 8b 44 24 08 49 89 84 24 a0 00
00 00 e9 36 fe ff ff 0f 1f 44 00 00 49 8b 94 24 98 00 00 00 49 8b 84 24 90 00
00 00 <80> 3a 48 0f 85 6f ff ff ff 48 b9 c7 c0 0f 00 00 00 0f 05 48 39 4a
Kindly need your support
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
