Re: seg fault on dsm_create call

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Max Fomichev <max(dot)fomitchev(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: seg fault on dsm_create call
Date: 2016-06-28 20:29:20
Message-ID: CA+TgmobB1JSCbJpJOKfJ1kwxF0Pvrdy6ZN-bUcX35Drf8R0bug@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 28, 2016 at 12:45 PM, Max Fomichev <max(dot)fomitchev(at)gmail(dot)com> wrote:
> On 28/06/16 19:24, Robert Haas wrote:
> Thanks.
> It works now with CurrentResourceOwner = ResourceOwnerCreate(NULL, "name of
> my extension")
>
> I am a little bit confused about test/modules/test_shm_mq, where
> CurrentResourceOwner is set up before dsm_attach, not dsm_create -

You need a resource owner for either dsm_attach or dsm_create.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Markus Wanner 2016-06-28 20:31:32 Re: IPv6 link-local addresses and init data type
Previous Message Alvaro Herrera 2016-06-28 20:05:11 Re: An unkillable connection caused replication delay on my replica