From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | Amit Langote <amitlangote09(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Retain dynamic shared memory segments for postmaster lifetime |
Date: | 2014-01-28 04:41:07 |
Message-ID: | CAA4eK1JU1HP6_M27S77SfG6+amZrAuNSnhZJ0hLV2aLsjf+r5w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jan 27, 2014 at 7:48 PM, Amit Langote <amitlangote09(at)gmail(dot)com> wrote:
> On Mon, Jan 13, 2014 at 2:50 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>> I have extended test (contrib) module dsm_demo such that now user
>> can specify during dsm_demo_create the lifespan of segment.
>
> Applied dsm_keep_segment_v1.patch and dsm_demo_v1.patch.
> Got the following warning when I tried above example:
>
> postgres=# select dsm_demo_create('this message is from session-new', 1);
> WARNING: dynamic shared memory leak: segment 1402373971 still referenced
> WARNING: dynamic shared memory leak: segment 1402373971 still referenced
> dsm_demo_create
> -----------------
> 1402373971
> (1 row)
Thanks for verification.
The reason is that resource owner has reference to segment till commit time
which leads to this warning. The fix is to remove reference from
resource owner when user calls this new API dsm_keep_segment, similar
to what currently dsm_keep_mapping does.
Find the updated patch to fix this problem attached with this mail.
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
Attachment | Content-Type | Size |
---|---|---|
dsm_keep_segment_v2.patch | application/octet-stream | 2.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2014-01-28 04:59:00 | Re: pg_basebackup and pg_stat_tmp directory |
Previous Message | Kouhei Kaigai | 2014-01-28 04:34:58 | Re: inherit support for foreign tables |