On Thu, Mar 9, 2017 at 2:19 PM, Peter Geoghegan <p...@bowt.ie> wrote: > Quite a lot of thought seems to have gone into making the > fd.c/resowner mechanism leak-proof in the face of errors. So, quite > apart from what that approaches misses out on, I really don't want to > change resource management too much. As I went into in my "recap", it > seems useful to change as little as possible about temp files.
I think this is just wishful thinking. resowners are backend-private, and they are robust as long as they are managing files accessed by a single backend. Trying to bend them into some kind of a state where they can manage a resource shared across multiple cooperating backends is fundamentally changing the model. What matters is not whether the old model was any good but whether the new one is any good. -- 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
