On Tue, May 2, 2017 at 5:50 AM, Konstantin Knizhnik <k.knizh...@postgrespro.ru> wrote: >> I don't see something with a bunch of hard-coded rules for particular type >> OIDs having any chance of being acceptable. > > Well, what I need is ...
Regarding this... > Definitely copying of code is bad flaw. It will be much better and easier > just to call three original functions instead of mixing gathering their code > into the new function. > But I failed to do it because ... ...and also this: I am sympathetic to the fact that this is a hard problem to solve. I'm just telling you that the way you've got it is not acceptable and nobody's going to commit it like that (or if they do, they will end up having to revert it). If you want to have a technical discussion about what might be a way to change the patch to be more acceptable, cool, but I don't want to get into a long debate about whether what you have is acceptable or not; I've already said what I think about that and I believe that opinion will be widely shared. I am not trying to beat you up here, just trying to be clear. > Thanks for your feedback. Sure thing. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
