| Subject: | Apache::Session::Postgres, prepare_cached statement conflict |
| Date: | Fri, 29 Apr 2016 16:19:36 +0200 |
| To: | bug-Apache-Session [...] rt.cpan.org |
| From: | larss <larsss31 [...] gmail.com> |
Hi,
in the “materialize” sub, the “materialize_sth” key of $self is used to keep a reference for the prepared and cached statement.
I’m having issue with a forked setup, where each child has its copy of the $self object, so, in each execution, triggers the “ prepare_cached” function, finding the reference undefined.
Postgresql then croaks because the statement had been previously created, but the forked child is unaware of that.
I had to change the “prepare_cached” to a simple “prepare” but i’d like to be able to choose this setup via some config parameter.
Thanks,
larss