On Fri, Jul 3, 2009 at 1:16 PM, Tom Lane<tgl@sss.pgh.pa.us> wrote:
> Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
>> Robert Haas wrote:
>>> What I've seen of Heikki's work thus far has led me to believe that
>>> his reasons for rejecting the patch were good ones, but I don't
>>> specifically what they were. It would be helpful, I think, to
>>> reiterate them or repost links to the relevant messages in the
>>> archives; it would also be great if we could get an estimate of how
>>> close the patch is to being committable. Does it still need massive
>>> work, or is it getting fairly close, or what? Are the issues code
>>> cleanliness/maintainability, bugs, missing functionality?
>
>> This is where we left off:
>> http://archives.postgresql.org/message-id/49A64D16.8010105@enterprisedb.com
>
> There were adjacent remarks suggesting that large other parts of the
> patch remained to be reviewed, as well.
> http://archives.postgresql.org/pgsql-hackers/2009-02/msg01268.php
Thanks to both of you, this is very helpful. Two other questions:
1. Are there any chunks of this functionality in this patch that seem
like they might be able to be severed and committed separately?
2. Was the latest version of this patch posted to the mailing list,
and if so can you provide a link?
Thanks,
...Robert