On Fri, Aug 15, 2003 at 11:58:42AM -0400, Kris Jurka wrote:
>
>
> On Fri, 15 Aug 2003, Tom Lane wrote:
>
> > > Should we only be doing PREPARE on queries that are known to be safe (e.g.
> > > single-statement SELECTs), or is it better to try to catch the errors and
> > > abandon the prepare? (more general, but sounds a bit hairy).
> >
> > Uh, don't you have to be prepared to catch errors in PREPARE anyway?
> > What if the command is syntactically or semantically wrong?
> >
>
> I believe he's suggesting that on a prepare error you would retry without
> prepare instead of just reporting it back to the caller.
Yes, that's what I meant.
I've realised it won't work transparently, though, as if you're in a
transaction the bad PREPARE will abort it.
-O
