| From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, Michael Blakeley <mike(at)blakeley(dot)com> |
| Subject: | Re: shmem_seq may be a bad idea |
| Date: | 2000-05-02 10:55:53 |
| Message-ID: | 390EB439.E42750F6@alumni.caltech.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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? Much
more likely to be of fixed length and compatible between versions, and
more likely to exist or not exist with the same behavior as the large
shared memory segment under discussion??
- Thomas
--
Thomas Lockhart lockhart(at)alumni(dot)caltech(dot)edu
South Pasadena, California
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2000-05-02 10:59:08 | Re: psql \l error |
| Previous Message | Bruce Momjian | 2000-05-02 10:55:47 | Re: Request for 7.0 JDBC status |