On 10/23/2014 09:21 PM, Robert Haas wrote: > Agreed - I think if you want an error check here it should use elog() > or ereport(), not Assert().
That's what I originally did, but it's too early for elog. I'm reluctant to just fprintf(...) to stderr, as there's no way for the user to suppress that, and it'll be emitted for each backend start. Though on the other hand it really is a "shouldn't happen" case. So the options seem to be ignoring the error silently or printing to stderr. -- Craig Ringer http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
