Skip site navigation (1) Skip section navigation (2)

dsm.c API tweak

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>,Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
Subject: dsm.c API tweak
Date: 2017-03-24 23:27:10
Message-ID: 20170324232710.32acsfsvjqfgc6ud@alvherre.pgsql (view raw, whole thread or download thread mbox)
Thread:
Lists: pgsql-hackers
Per 
https://postgr.es/m/CAEepm=11ma_Z1HoPxPcSCANnh5ykHORa=HcA1U1V1+5S_jwPuA@mail.gmail.com
it seems that the dsm.c API is a bit inconvenient right now.  I proposed
in the first patch in that thread to change the API so that a segment is
marked as "pinned" if created with no ResourceOwner set as current;
which is essentially the same as creating a fake one, then marking the
segment as pinned.

Thomas agrees with me, so I propose this patch as preparatory work for
the autovacuum/BRIN stuff I'm interested in.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


Responses

pgsql-hackers by date

Next:From: Peter EisentrautDate: 2017-03-24 23:31:37
Subject: Re: [PATCH] Transaction traceability - txid_status(bigint)
Previous:From: Michael PaquierDate: 2017-03-24 23:15:18
Subject: Re: Potential data loss of 2PC files

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group