Re: Listen / Notify - what to do when the queue is full
От | Andrew Chernow |
---|---|
Тема | Re: Listen / Notify - what to do when the queue is full |
Дата | |
Msg-id | 4B016324.5020403@esilo.com обсуждение исходный текст |
Ответ на | Re: Listen / Notify - what to do when the queue is full ("Greg Sabino Mullane" <greg@turnstep.com>) |
Ответы |
Re: Listen / Notify - what to do when the queue is full
|
Список | pgsql-hackers |
Greg Sabino Mullane wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: RIPEMD160 > > >> We still need to decide what to do with queue full situations in >> the proposed listen/notify implementation. I have a new version >> of the patch to allow for a variable payload size. However, the >> whole notification must fit into one page so the payload needs >> to be less than 8K. > > That sounds fine to me, FWIW. > Agreed. Thank you for all your work. >> 1) drop new notifications if the queue is full (silently or with rollback) > > I like this one best, but not with silence of course. While it's not the most > polite thing to do, this is for a super extreme edge case. I'd rather just > throw an exception if the queue is full rather than start messing with the +1 -- Andrew Chernow eSilo, LLC every bit counts http://www.esilo.com/
В списке pgsql-hackers по дате отправления: