Hello Robert,
I wish to agree, but my interpretation of the previous code is that
they were ignored before, so ISTM that we are stuck with keeping the
same unfortunate behavior.
I don't agree. I'm not in a huge hurry to fix all the places where
pgbench currently lacks error checks just because I don't have enough to
do (hint: I do have enough to do), but when we're adding more
complicated syntax in one particular place, bringing the error checks in
that portion of the code up to scratch is an eminently sensible thing to
do, and we should do it.
Ok. I'm in favor of that anyway. It is just that was afraid that changing
behavior, however poor the said behavior, could be a blocker.
Also, please stop changing the title of this thread every other post.
It breaks threading for me (and anyone else using gmail), and that
makes the thread hard to follow.
Sorry. It does not break my mailer which relies on internal headers, but
I'll try to be compatible with this gmail "features" in the future.
--
Fabien.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
