On 3/21/13 2:38 PM, Robert Haas wrote:
Also, while I think that MOST people will probably want a SIGHUP right after SET PERSISTENT, I am not sure that EVERYONE will want that. If you want it and it doesn't happen automatically, you can always do it by hand.
This is a fair position, and since that's how the feature as written right now works that helps. I think proceeding this way needs to hand some sort of hint back to the user though, telling them the change isn't active until SIGHUP. The path I don't want to see if where someone uses SET PERSISTENT and can't figure out why nothing changed. It should be as obvious as we can make it to someone that the explicit reload is necessary.
-- Greg Smith 2ndQuadrant US g...@2ndquadrant.com Baltimore, MD PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
