> well, true - but also, statically allocated table, without any predefined > size (with #DEFINE) , and no boundary check - is bad as well. > I suppose , this code is easy enough to let it be with your changes, but I > would still call it not pretty.
Well, it might merit a comment. > Actually - if you did profile postgresql with bunch of queries, I wouldn't > mind to see results of it - I don't know whether it makes sense to send that > to the list (I would think it does), but if it is too big, or something - > you could send it to me in private. What I'd really like to do is develop some tests based on a publicly available dataset. Any suggestions? ...Robert -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
