Robert Haas <robertmh...@gmail.com> writes:
> That sounds good, except for the part about nobody doing anything
> about the 9.0 open issues. Those issues are:
> * Backup procedure is wrong? - Nobody's been able to clearly
> articulate what the problem is, and according to Fujii Masao it's been
> this way since 8.2.
Just because it's old doesn't mean it's not a bug ;-). Normally I would
say that a pre-existing documentation problem isn't a release blocker,
but in this case that procedure is likely to become of interest to a
whole lot more people than it was before, thanks to SR/HS. So we need
to understand whether there's a problem and fix it.
> * Walreceiver crashes in AIX - The person who originally reported this
> problem has been slow to get back to us with the information needed to
> figure out what is going on.
Yes. If he doesn't provide adequate data, and we can't reproduce it
elsewhere, we should not consider this a release blocker.
> * BUG #5595: Documentation is not installs from VPATH build. - I'm not
> sure this is really a release-blocker, but either way, I have been
> assuming it's Peter's issue to fix.
I believe this is a regression from prior branches, probably caused by
the switch away from distributing the prebuilt docs as sub-tarballs.
As such, it's at least a candidate release-blocker.
> * trace_recovery_messages inconsistency - This one seems like a simple
> case of deciding what makes most sense, and doing it. We should
> definitely fix this before the wrap.
Agreed, it's a matter of getting some consensus.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
