Re: pg11.1: dsa_area could not attach to segment

From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
To: Sergei Kornilov <sk(at)zsrv(dot)org>
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg11.1: dsa_area could not attach to segment
Date: 2019-02-12 00:07:35
Message-ID: CAEepm=0JvtVBmhy6wwiuNOqze8g-QJ1Ss_wWSBVJ2znSUQpzzw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Feb 12, 2019 at 10:57 AM Thomas Munro
<thomas(dot)munro(at)enterprisedb(dot)com> wrote:
> bogus shm_open() EEXIST from the OS

Strike that particular idea... it'd be the non-DSM_OP_CREATE case, and
if the file was somehow bogusly not visible to us we'd get ENOENT and
that'd raise an error, and we aren't seeing that.

--
Thomas Munro
http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tsunakawa, Takayuki 2019-02-12 00:49:27 RE: Protect syscache from bloating with negative cache entries
Previous Message Thomas Munro 2019-02-11 23:57:51 Re: pg11.1: dsa_area could not attach to segment