| От | Chris Marcellino |
|---|---|
| Тема | Re: Feature: POSIX Shared memory support |
| Дата | |
| Msg-id | 12C1D0E7-0206-4EEE-974F-DC5BD06962C2@levelview.com обсуждение исходный текст |
| Ответ на | Re: Feature: POSIX Shared memory support (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | pgsql-patches |
Attached is a beta of the POSIX shared memory layer. It is 75% the original sysv_shmem.c code. I'm looking for ways to refactor it down a bit, while changing as little of the tried-and-tested code as possible. I though I'd put it out there for comments. Of course, unfortunately it is more complicated than the original as it uses both sets of API. Also, I haven't tested the crash recovery thoroughly. The POSIX code could be used Windows-style (i.e. no crash recovery) if one ifdef'd out the SysV calls properly, if they had such a POSIX-only platform they needed to run Postgres on. Using both API is certainly not ideal. You mentioned, > We've speculated on occasion about using file locking in some form > as a > substitute mechanism for detecting this, but that seems to just bring > its own set of not-too-portable assumptions What sort of file locking did you have in mind? Do you think this might be worth me trying? Thanks for your help, Chris Marcellino
В списке pgsql-patches по дате отправления:
Сайт использует файлы cookie для корректной работы и повышения удобства. Нажимая кнопку «Принять» или продолжая пользоваться сайтом, вы соглашаетесь на их использование в соответствии с Политикой в отношении обработки cookie ООО «ППГ», в том числе на передачу данных из файлов cookie сторонним статистическим и рекламным службам. Вы можете управлять настройками cookie через параметры вашего браузера