Re: Re: PATCH: pageinspect / add page_checksum and bt_page_items(bytea)

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: Re: PATCH: pageinspect / add page_checksum and bt_page_items(bytea)
Дата
Msg-id CA+TgmoYG+PP6==-3v2ZsB1FD8ufPoKFWXEBsUKLwr5imBeDV8A@mail.gmail.com
обсуждение исходный текст
Ответ на [HACKERS] PATCH: pageinspect / add page_checksum and bt_page_items(bytea)  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
Ответы Re: Re: PATCH: pageinspect / add page_checksum andbt_page_items(bytea)
Список pgsql-hackers
On Tue, Apr 4, 2017 at 9:32 AM, David Steele <david@pgmasters.net> wrote:
> My goal is to help people focus on patches that have a chance.  At this
> point I think that includes poking authors who are not being responsive
> using the limited means at my disposal.

+1.  Pings on specific threads can help clear things up when, for
example, the author and reviewer are each waiting for the other.  And,
as you say, they also help avoid the situation where a patch just
falls off the radar and misses the release for no especially good
reason, which naturally causes people frustration.

I think your pings have been quite helpful, although I think it would
have been better in some cases if you'd done them sooner.  Pinging
after a week, with a 3 day deadline, when there are only a few days
left in the CommitFest isn't really leaving a lot of room to maneuver.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Vicky Vergara
Дата:
Сообщение: Re: Instead of DROP function use UPDATE pg_proc in anupgrade extension script
Следующее
От: Robert Haas
Дата:
Сообщение: Re: partitioned tables and contrib/sepgsql