Re: shmem_seq may be a bad idea - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: shmem_seq may be a bad idea
Date
Msg-id Pine.LNX.4.21.0005022334270.362-100000@localhost.localdomain
Whole thread Raw
In response to Re: shmem_seq may be a bad idea  (Thomas Lockhart <lockhart@alumni.caltech.edu>)
List pgsql-hackers
Thomas Lockhart writes:

> > A while ago while thinking about a way to make ipcclean better I thunk
> > that perhaps the postmaster should write the keys of the segments it gets
> > to a flat-text file. If it somehow crashes and loses track of what it
> > allocated before it can use that information to clean up. Not sure how
> > often that would take effect but it's very socially friendly.
> 
> Hmm. Could we write this to a separate shared memory segment?

But how would ipcclean get to the key of *that* segment? I was thinking
file because that'd always be in a known location and could also be
accessible to humans to sort things out by hand or debug stuff.


-- 
Peter Eisentraut                  Sernanders väg 10:115
peter_e@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: RE: [PATCHES] relation filename patch
Next
From: Tom Lane
Date:
Subject: Re: Proposal for fixing intra-query memory leaks