Re: BUG #16264: Server closed the connection unexpectedly

Thanks Tom for your prompt response and my apologies for the lack of
details (indeed, I didn't give you much to help you!). These are what I can
tell you, let me know if you have any questions.

1. I'm running macOS 10.15.3
2. Everything was working fine with PostgreSQL version 12.1 and since
I have installed 12.2 on two machines (with identical os), many queries
induce server process to get terminated by signal 9 (according to log).
This is the case on the two machines that I'm running 12.2 Unfortunately,
the log doesn't say more than that (see below an extract).
3. I have used the installer certified by EnterpriseDB to
install PostgreSQL
4. I didn't make any changes to the postgresql.conf file
5. The issue shows up with pgAdmin 4 and psycopg2 (Python 3.7).

This an extract of the log file:

*2020-02-19 18:24:57.449 EST [175] LOG: server process (PID 3032) was
terminated by signal 9: Killed: 9*
*2020-02-19 18:24:57.449 EST [175] DETAIL: Failed process was running: set
timezone to 'Europe/Paris';*
* select*
* extract(year from fd.datetime_starting) as year,*
* rfd.market,*
* rfd.fundamental_subtype as prod_type,*
* sum(fd.value) as installed_capacity*
* from*
* edb.tbl_ref_fundamental_data rfd,*
* cwe_uk.tbl_hist_datetime_fundamental_data fd*
* where*
* rfd.id <http://rfd.id> = fd.data_id and*
* rfd.value_type = 'Actual' and*
* rfd.fundamental_type = 'Installed capacity' and*
* rfd.commodity = 'Power' and*
* rfd.market in ('AT', 'BE', 'FR', 'DE', 'NL', 'CH', 'UK')
and*
* rfd.term = 'Annual' and*
* fd.datetime_starting::date >= '2000-01-01' and*
* fd.datetime_starting::date <= '2020-02-18'*
* group by*
* extract(year from fd.datetime_starting),*
* rfd.market,*
* rfd.fundamental_subtype*
* order by*
* extract(year from fd.datetime_starting),*
* rfd.market,*
* rfd.fundamental_subtype;*
*2020-02-19 18:24:57.449 EST [175] LOG: terminating any other active
server processes*
*2020-02-19 18:24:57.449 EST [2986] WARNING: terminating connection
because of crash of another server process*
*2020-02-19 18:24:57.449 EST [2986] 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.*

Best regards,
[image: Pyxidr]

ROBIN DUQUETTE
CEO
E: robin(dot)duquette(at)pyxidr(dot)com
C: +1 (514) 262-0418 <+1+(514)+262-0418>
[image: Pyxidr Website] <http://pyxidr.com/> [image: Pyxidr Telegram]
<http://t.me/Pyxidr> [image: Robin Duquette LinkedIn]
<https://www.linkedin.com/in/robinduquette/> [image: Robin Duquette Medium]
<https://medium.com/@robinduquette>

On Wed, Feb 19, 2020 at 11:26 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> > I just installed postgresql 12.2 (from 12.1) and I get many "server
> closed
> > the connection unexpectedly" when executing queries in pgAdmin or using
> > psycopg2 (in Python). I didn't get this issue with 12.1.
>
> This might well be a bug, but there's nothing we can do about it with
> no details. There's some advice about submitting useful bug reports
> here:
>
> https://wiki.postgresql.org/wiki/Guide_to_reporting_problems
>
> regards, tom lane
>