Re: ECPG bug fix: DECALRE STATEMENT and DEALLOCATE, DESCRIBE
От | Andrew Dunstan |
---|---|
Тема | Re: ECPG bug fix: DECALRE STATEMENT and DEALLOCATE, DESCRIBE |
Дата | |
Msg-id | cc410b1a-cdbd-3fd7-a688-3d862cc15a4a@dunslane.net обсуждение исходный текст |
Ответ на | Re: ECPG bug fix: DECALRE STATEMENT and DEALLOCATE, DESCRIBE (Bruce Momjian <bruce@momjian.us>) |
Список | pgsql-hackers |
On 8/9/21 6:15 PM, Bruce Momjian wrote: > On Tue, Aug 10, 2021 at 12:03:24AM +0200, Michael Meskes wrote: >> I'd like to apologize for not answering your email the way I should >> have. Honestly it never occurred to me. Maybe that's because I'm used >> to other procedures, or because I never had to converse with the RMT, >> or maybe, quite simple, because I lacked the time to think it through, >> the original issue that kind of started this whole mess. > Agreed. When the RMT contacts me, I assume it is something that is time > and release critical so I give them as much detail as I can, and a > timeline when they will get more information. If you are not focused on > the RMT process, it might not be clear why that is important. > That's what you should be doing. If nothing else comes from this colloquy it should make all committers aware of the process. The reason we have an RMT, as I understand it, is to prevent the situation we had years ago when things sometimes dragged on almost interminably after feature freeze. cheers andrew
В списке pgsql-hackers по дате отправления: