> I think this patch needs to be looked upon by committer now. I have > done review and added some code in this patch as well long back, just > see the e-mail [1], patch is just same as it was in October 2015. I > think myself and Michael are in agreement that this patch solves the > reported problem. There is one similar problem [2] reported by Heikki > which I think can be fixed separately. > [...] > Let me know if you think anything more from myside can help in moving > patch.
+1, same here. Lets see whats committer's opinion. -- Best regards, Aleksander Alekseev http://eax.me/ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
