Re: Re: PATCH: pageinspect / add page_checksum and bt_page_items(bytea) - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Re: PATCH: pageinspect / add page_checksum and bt_page_items(bytea)
Date
Msg-id CA+TgmoYG+PP6==-3v2ZsB1FD8ufPoKFWXEBsUKLwr5imBeDV8A@mail.gmail.com
Whole thread Raw
In response to [HACKERS] PATCH: pageinspect / add page_checksum and bt_page_items(bytea)  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
Responses Re: Re: PATCH: pageinspect / add page_checksum andbt_page_items(bytea)  (David Steele <david@pgmasters.net>)
List 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 by date:

Previous
From: Vicky Vergara
Date:
Subject: Re: Instead of DROP function use UPDATE pg_proc in anupgrade extension script
Next
From: Robert Haas
Date:
Subject: Re: partitioned tables and contrib/sepgsql