??>> but are you sure that restarting txn in this case is right, and when
??>> such stuff happens at all?
LPP> Heh, if you ask me the best solution would be if Postgres
LPP> just shut up about it without affecting the txn.
LPP> But alas, this isn't the case.
hmm, postgres documentation says:
> LPP> What can I do about it with the new Postmodern code?
>
> hmm, iirc this error was addressed in executor-exec-prepared in pm-sql.lisp,
> but you moved it into pm-transaction.lisp to restart txn in case of this
> error, right?
Yes.
> and then i've removed it when merging, sorry..
>
> if s
LPP> What can I do about it with the new Postmodern code?
hmm, iirc this error was addressed in executor-exec-prepared in pm-sql.lisp,
but you moved it into pm-transaction.lisp to restart txn in case of this
error, right?
and then i've removed it when merging, sorry..
if so, add it into into p
Here's an old one happening again:
debugger invoked on a CL-POSTGRES:DATABASE-ERROR in thread #:
Database error 42P05: prepared statement "TREE23FIRST" already exists
Query: SELECT qi, bob, value FROM tree23 INNER JOIN blob ON bid = value ORDER
BY qi ASC
LIMIT 10
What can I do about it with
