Re: Peripatus: Can someone look? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Peripatus: Can someone look?
Date
Msg-id 2643.1569944813@sss.pgh.pa.us
Whole thread Raw
In response to Peripatus: Can someone look?  (Larry Rosenman <ler@lerctr.org>)
Responses Re: Peripatus: Can someone look?  (Larry Rosenman <ler@lerctr.org>)
List pgsql-hackers
Larry Rosenman <ler@lerctr.org> writes:
> My Buildfarm animal (peripatus) has been failing check since yesterday.
> Can someone look at it?

It's been doing this in parallel queries, in v11 and up:

2019-09-29 19:00:15.534 CDT [49513:1] ERROR:  could not open shared memory segment "/PostgreSQL.1225945786": Permission
denied
2019-09-29 19:00:15.535 CDT [48596:491] pg_regress/partition_prune ERROR:  parallel worker failed to initialize
2019-09-29 19:00:15.535 CDT [48596:492] pg_regress/partition_prune HINT:  More details may be available in the server
log.
2019-09-29 19:00:15.535 CDT [48596:493] pg_regress/partition_prune CONTEXT:  PL/pgSQL function
explain_parallel_append(text)line 5 at FOR over EXECUTE statement 
2019-09-29 19:00:15.535 CDT [48596:494] pg_regress/partition_prune STATEMENT:  select explain_parallel_append('select
avg(ab.a)from ab inner join lprt_a a on ab.a = a.a where a.a in(1, 0, 0)'); 
2019-09-29 19:00:15.535 CDT [48596:495] pg_regress/partition_prune WARNING:  could not remove shared memory segment
"/PostgreSQL.1225945786":Permission denied 

which looks like an external problem to me --- certainly, nothing
we changed yesterday would explain it.  Did you change anything
about the system configuration, or do a software update?

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Optimize partial TOAST decompression
Next
From: Larry Rosenman
Date:
Subject: Re: Peripatus: Can someone look?