Re: pg_filedump 9.3: checksums (and a few other fixes) - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: pg_filedump 9.3: checksums (and a few other fixes)
Date
Msg-id 20130708185228.GE18471@eldon.alvh.no-ip.org
Whole thread Raw
In response to Re: pg_filedump 9.3: checksums (and a few other fixes)  (Peter Geoghegan <pg@heroku.com>)
Responses Re: pg_filedump 9.3: checksums (and a few other fixes)
Re: pg_filedump 9.3: checksums (and a few other fixes)
List pgsql-hackers
Peter Geoghegan escribió:
> On Mon, Jul 8, 2013 at 10:28 AM, Jeff Davis <pgsql@j-davis.com> wrote:
> > I see this patch is still "waiting on author" in the CF. Is there
> > something else needed from me, or should we move this to "ready for
> > committer"?
> 
> Well, obviously someone still needs to think through the handling of
> the infoMask bits.

Well, Tom opined in
http://www.postgresql.org/message-id/23249.1370878717@sss.pgh.pa.us that
the current patch is okay.  I have a mild opinion that it should instead
print only SHR_LOCK when both bits are set, and one of the others when
only one of them is set.  But I don't have a strong opinion about this,
and since Tom disagrees with me, feel free to exercise your own (Jeff's)
judgement.

Tom's the only available committer in this case anyway.  [Actually,
pgfoundry.org says it's a zero-people team in the pgfiledump project
right now, but I'm hoping that's just a temporary glitch.]

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: [PATCH] pgbench --throttle (submission 7 - with lag measurement)
Next
From: Mike Blackwell
Date:
Subject: Re: [v9.4] row level security