Hi, From: Simone Tregnago <[EMAIL PROTECTED]> Subject: Re: [Pgpool-general] insert_lock leaks Date: Thu, 29 May 2008 11:19:02 +0200
> I had re-enabled the insert_lock parameter: without this option serial > numbers changes between backends and data integrity will be lost in some > relations. > Now I have to manually search deadlocked processes and kill them. This > happens almost one time a day. > If someone could suggest something... would be very appreciated. Could you provide a reproducible program? Regards, -- Yoshiyuki Asaba [EMAIL PROTECTED] > > Thanks in advance > Simone Tregnago > > Simone Tregnago wrote: > > Version: 2.1 beta2 > > I think I've encountered a leak related to the 'auto insert lock' > > feature. With the insert_lock option enabled, after 1 day, I found a few > > locked tables that I wasn't able to unlock. Then, I disabled the option, > > and until now I haven't found any locked table again. > > Note that my ERP takes the connections always opened; so, it could be a > > bug that leaves the locks active until the connection closes. > > > > Thanks, > > Simone Tregnago > > _______________________________________________ > > > _______________________________________________ > Pgpool-general mailing list > [email protected] > http://pgfoundry.org/mailman/listinfo/pgpool-general _______________________________________________ Pgpool-general mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-general
