On Wed, Sep 7, 2011 at 4:15 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Robert Haas <robertmh...@gmail.com> writes: >> On Wed, Sep 7, 2011 at 3:42 PM, Alvaro Herrera >> <alvhe...@commandprompt.com> wrote: >>> A mishandled encoding conversion could be problematic, so that needs to >>> be carefully considered (perhaps just shut off unconditionally). > >> It's not really a problem for the postmaster if something just plain >> old fails. Where we get into trouble is if it manages to (a) crash, >> (b) take an excessive amount of time to complete, or (c) screw up the >> postmaster state in some way we can't recover from. But if any of >> those are an issue then, yeah, just shut it off. > > Keep in mind that in the postmaster, elog(ERROR) *is* a crash.
Right... but a function that returns -1 to indicate that something didn't work should be OK, as long as whatever it does is otherwise extremely boring. -- 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
