Re: debugging: prepared statement "dbdpg_7" already exists

"Greg Sabino Mullane" <greg-738XdyZ4GzZWk0Htik3J/[email protected]> writes:
> This is caused because a statement handle thinks that 7 is the next
> available number, but someone else on the same connection has
> already created it. The most likely cause is if you are using
> forks. If not, then a repeatable test case would be great. There is
> one hack I am considering adding that may fix it, but I need to
> verify the problem first.

Prepared statements break immediately using pgpool.

> No: the idea is to keep things like prepared names as transparent
> and hands-off as possible, and leave the name juggling to DBD::Pg.
> That's the theory anyway, it might be failing here. :)

While I think the ideal of not bothering people with it is admirable,
I would love to see the ability to easily set the name during a
regular prepare, because I would like to be able to take advantage of
pgpool, and I would rather not have to do a double prepare for every
single statement.

Mike
-- 
I don't need no makeup, I've got real scars