Re: Error: dsa_area could not attach to a segment that has been freed

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Gaddam Sai Ram <gaddamsairam(dot)n(at)zohocorp(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Error: dsa_area could not attach to a segment that has been freed
Date: 2017-09-20 12:59:58
Message-ID: CA+TgmoaPOHn8OJW5B_K6yStZFQtK3N6qGu5mfECsY_jdgXXuRA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Sep 20, 2017 at 5:54 AM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
> By the way, dsa.c really needs a cross-reference to shm_toc.c and vice
> versa. With a hint as to when each is appropriate.

/me blinks.

Aren't those almost-entirely-unrelated facilities?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-09-20 13:14:44 Re: Page Scan Mode in Hash Index
Previous Message Peter Eisentraut 2017-09-20 12:59:56 Re: sync process names between ps and pg_stat_activity