> Yes. There's not going to be any more commitfests for this release, so
> the next commitfest is for 9.1.
Perfect! Where could I find such information? I mean: how could I know
it?
> (don't worry about the lack of enthusiasm for the patch, people are just
> very busy with 9.0 and don't have the
Leonardo F wrote:
> But there's something I don't understand: I didn't add the patch to the next
> CommitFest because I thought it could never be added in 9.0 (because it adds a
> new "feature" which has never been discussed). Hence I thought it should have
> been "discussed" (not properly "reviewe
> As outlined in the "Submission timing" section, you're
> asking about something during the wrong time to be doing so--that's why
> you're
> not getting any real feedback. Add your patch to the next CommitFest by
> linking
> to your message at https://commitfest.postgresql.org/
Ok!
But th
Leonardo F wrote:
Could at least the message:
http://archives.postgresql.org/pgsql-hackers/2010-02/msg00766.php
be added to the TODO page, under
"Improve CLUSTER performance by sorting to reduce
random I/O" ?
It would be sad if the patch got lost...
You should read http://wiki.postgresql.org/
I really thought this would have caused some interest, since
- this item is in the TODO list
- the improvement for CLUSTER in some scenarios is 800%,
and maybe more (if I didn't do anything wrong, of course...)
Could at least the message:
http://archives.postgresql.org/pgsql-hackers/2010-02/msg00
