Re: shared memory message queues
От | Robert Haas |
---|---|
Тема | Re: shared memory message queues |
Дата | |
Msg-id | CA+TgmoYEVDuUkJgwpPz+NUs70Puu6JV0oFhsh4TLsKX8Tk7Xqg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: shared memory message queues (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: shared memory message queues
Re: shared memory message queues |
Список | pgsql-hackers |
On Tue, Dec 17, 2013 at 11:51 AM, Robert Haas <robertmhaas@gmail.com> wrote: > Unless anyone wants to further kibitz the naming here, I'm thinking > this part is ready to commit. I'll rebase and update the remaining > patches after that's done. OK, so I committed that. Per Andres's gripe about lack of overall design documentation, I added several large comment blocks to shm-mq-v1.patch; the updated version is here attached as shm-mq-v2.patch. test-shm-mq-v1.patch no longer compiles due to the naming changes in that patch, so here's test-shm-mq-v2.patch with a one-line change to compensate. These are intended to apply on top of shm-toc-v1.patch, which I am not reposting here since it's unchanged, and I'm unaware of any fixes that are needed there except possibly for some further elaboration of the comments. It sounds like most people who have looked at this stuff are broadly happy with it, so I'd like to push on toward commit soon, but it'd be helpful, Andres, if you could review the comment additions to shm-mq-v2.patch and see whether those address your concerns. If so, I'll see about improving the overall comments for shm-toc-v1.patch as well to clarify the points that seem to have caused a bit of confusion; specific thoughts on what ought to be covered there, or any other review, is most welcome. Thanks, -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Вложения
В списке pgsql-hackers по дате отправления: