This is the patch I've tested successfully on OpenERP 5.0.11. You just need to "killall postgres" to test its behaviour :-)
Best regards, -- Florent 2011/11/16 Florent <[email protected]> > Hello Nicolas, > > AFAICT it's fixed in trunk > http://git.hellug.gr/?p=xrg/openobject-server;a=commit;h=59895822466e8427fa > > If the question is related to v5.0, I can provide a patch. > > Regards, > > -- > Florent > > > 2011/11/8 Nicolas Bessi <[email protected]> > >> Hello, >> >> Last Debian security update as restarted PostgreSQL. Some user have maybe >> encounter troubles with ther instances (having cursor close error etc.). >> In such case is it legitimate to have OpenERP to try to flush is pooler >> and try to reinitiate connexion for a given duration. >> If not possible should the main OpenERP process stop itself etc. I think >> it is important to have such reflexion as ERP must be high disponnibility >> application. >> >> Any reaction are welcome. >> >> >> Regards >> >> Nicolas >> >>
oerp5_discard_closed_connections.diff
Description: Binary data
_______________________________________________ Mailing list: https://launchpad.net/~openerp-expert-framework Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-expert-framework More help : https://help.launchpad.net/ListHelp
