pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Yuli Khodorkovskiy <yuli.khodorkovskiy@crunchydata.com>
Cc: pgsql-bugs@lists.postgresql.org, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Subject: Re: BUG #15804: Assertion failure when using logging_collector with EXEC_BACKEND
Date: Thu, 16 May 2019 12:56:17 +0900
Message-ID: <20190516035617.GC1415@paquier.xyz> (raw)
In-Reply-To: <28927.1557977558@sss.pgh.pa.us>
References: <15804-3721117bf40fb654@postgresql.org>
	<27CD45B5-88F7-4A09-8B31-EFE41FC37FE1@crunchydata.com>
	<26332.1557863524@sss.pgh.pa.us>
	<20190515073125.GA1517@paquier.xyz>
	<4643.1557931189@sss.pgh.pa.us>
	<20190516013808.GA1415@paquier.xyz>
	<20190516021903.GB1415@paquier.xyz>
	<28927.1557977558@sss.pgh.pa.us>

On Wed, May 15, 2019 at 11:32:38PM -0400, Tom Lane wrote:
> Michael Paquier <michael@paquier.xyz> writes:
> > Also, I am noticing another consequence as the handling of backend
> > variable files also suffers consequences:
> > could not open backend variables file
> > "pgsql_tmp/pgsql_tmp.backend_var.21912.1": No such file or directory
> 
> Um ... where/how are you seeing that?

On HEAD with EXEC_BACKEND, just like that:
$ cd src/bin/pg_ctl && PROVE_TESTS=t/004_logrotate.pl make check
$ cat tmp_check/log/004_logrotate_primary.log
2019-05-16 12:44:03.427 JST [26433] LOG:  redirecting log output to
logging collector process
2019-05-16 12:44:03.427 JST [26433] HINT:  Future log output will
appear in directory "log".
could not open backend variables file
"pgsql_tmp/pgsql_tmp.backend_var.26433.1": No such file or directory

The test is able to pass, but we have a race condition between the
moment the backend file gets saved and the moment we allow it to be
read.   I have not spent much time checking the stack between
InitializeMaxBackends() and RemovePgTempFiles() in postmaster.c, but
57431a9 triggers the failure.
--
Michael

Attachments:

  [application/pgp-signature] signature.asc (832B, ../20190516035617.GC1415@paquier.xyz/2-signature.asc)
  download

view thread (40+ messages)  latest in thread

Message-ID: <20190516035617.GC1415@paquier.xyz>
Permalink:  ../20190516035617.GC1415@paquier.xyz/
Also on:    postgresql.org/message-id/20190516035617.GC1415@paquier.xyz

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: michael@paquier.xyz, tgl@sss.pgh.pa.us, yuli.khodorkovskiy@crunchydata.com, peter.eisentraut@2ndquadrant.com
  Subject: Re: BUG #15804: Assertion failure when using logging_collector with EXEC_BACKEND
  In-Reply-To: <20190516035617.GC1415@paquier.xyz>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox