Tom Lane wrote:
Magnus Hagander <[EMAIL PROTECTED]> writes:
Not sure if this is platform-specific, but I keep being annoyed by not
being able to actually *view* the patches in the queue. I have to
download them, and then open them separately. I can't just view them in
the browser, because they're all named ".bin" and come out as mime type
"application/octet-stream".
Yeah, it happens that way for me too. The other huge, huge problem with
it is the lack of stability of URLs for the items in the list, which
makes it difficult to identify which item you're talking about.
yeah that is fairly annoying :-(
Personally I'd be happier with an editable wiki page consisting of links
to the original messages in the mail list archives, plus free-format
annotations (such as status). This should be trivial to set up and
reasonably flexible. With experience we might find we need something
fancier, but let's not overdesign our solution at the start.
I will see if I can come up with a proposal on the developer wiki for a
list that looks like that tomorrow.
_IF_ we are looking for an (over)designed solution I just resurrected
what was left over from the last years discussion on that topic (and the
creating of the now defunct tracker mailinglist).
What was discussed back then was a set of requirements for a
(bug|feature) tracker and based on that I hacked up a prototype using a
modified/enhanced version of bugzilla 3.0.
some of the discussions/criterias from back than are summarized on:
http://developer.postgresql.org/index.php/TrackerDiscussion
the demo installation itself is on:
http://trackerdemo.postgresql.org
with a modified bug submission form on
http://pgweb.kaltenbrunner.cc/support/submitbug
basic concepts and docs are on the wiki too.
Stefan
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
