On Fri, Mar 22, 2013 at 8:06 AM, Simon Riggs <si...@2ndquadrant.com> wrote: >> Hmm. If a malicious user could hurt performance for other sessions with >> a bad setting of commit_delay, then USERSET is clearly a bad idea. >> But it still seems like it could be SUSET rather than SIGHUP. > > Agreed; everybody gets what they want. Committed.
This is fine with me, too, and I agree that it's warranted... but your commit message supposes that this behavior is new in 9.3, and I think it dates to 9.2. I'm not inclined to think the issue is serious enough to back-patch (and risk breaking current installations) but I thought that it worth mentioning.... -- 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
