Re: Segmentation fault with parallelism PG 10.4

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: "Heinemann, Manfred (IMS)" <HeinemannM@xxxxxxxxxx>
Subject: Re: Segmentation fault with parallelism PG 10.4
From: Tom Lane <tgl@xxxxxxxxxxxxx>
Date: Tue, 19 Jun 2018 11:14:05 -0400
Cc: "pgsql-admin@xxxxxxxxxxxxxxxxxxxx" <pgsql-admin@xxxxxxxxxxxxxxxxxxxx>
Comments: In-reply-to "Heinemann, Manfred (IMS)" <HeinemannM@xxxxxxxxxx> message dated "Tue, 19 Jun 2018 14:49:53 -0000"
In-reply-to: <44f8d9c203124535b497f2a79ceac59d@THALASSA.omni.imsweb.com>
References: <8577044f0d2f4fe3919c53c2f7a642e5@THALASSA.omni.imsweb.com> <1476.1528825515@sss.pgh.pa.us> <8493b91fb47d432297fbd4d96b7cb553@THALASSA.omni.imsweb.com> <44f8d9c203124535b497f2a79ceac59d@THALASSA.omni.imsweb.com>

"Heinemann, Manfred (IMS)" <HeinemannM@xxxxxxxxxx> writes:
> Is this stack trace helpful at all?

No, because it isn't actually a stack trace, just the top frame.  See

https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend

			regards, tom lane

Follow-Ups:
- RE: Segmentation fault with parallelism PG 10.4
  - From: Heinemann, Manfred (IMS)

References:
- Segmentation fault with parallelism PG 10.4
  - From: Heinemann, Manfred (IMS)
- Re: Segmentation fault with parallelism PG 10.4
  - From: Tom Lane
- RE: Segmentation fault with parallelism PG 10.4
  - From: Heinemann, Manfred (IMS)
- RE: Segmentation fault with parallelism PG 10.4
  - From: Heinemann, Manfred (IMS)

Prev by Date: RE: Segmentation fault with parallelism PG 10.4
Next by Date: Re: pgAdmin4 Docker deployment issue
Previous by thread: RE: Segmentation fault with parallelism PG 10.4
Next by thread: RE: Segmentation fault with parallelism PG 10.4
Index(es):
- Date
- Thread

[Index of Archives] [KVM ARM] [KVM ia64] [KVM ppc] [Virtualization Tools] [Spice Development] [Libvirt] [Libvirt Users] [Linux USB Devel] [Linux Audio Users] [Yosemite Questions] [Linux Kernel] [Linux SCSI] [XFree86]