Re: [Re] Re: PREPARE and transactions - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: [Re] Re: PREPARE and transactions
Date
Msg-id d233ee25ff9740f0343193d8fc2439f1@biglumber.com
Whole thread Raw
In response to Re: [Re] Re: PREPARE and transactions  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [Re] Re: PREPARE and transactions  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [Re] Re: PREPARE and transactions  ("Jeroen T. Vermeulen" <jtv@xs4all.nl>)
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> It seems like we are closing in on an agreement that that is what
> should happen.
I was originally unhappy with the current situation, but now I think
it is the best. Any changes will also cause a huge further headache
for driver/application writers, as we already have a released version
(and probably at least one more) with the current behavior. I'd be
all for making a DoesStatementExist(text) function, but changing
the behavior now may be closing the barn doors too late in the game,
and I've yet to see a totally convincing argument for a change,
considering that prepared statements are very explicitly declared
and cannot be seen outside of their own connection.
- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200406242200
-----BEGIN PGP SIGNATURE-----
iD8DBQFA24ehvJuQZxSWSsgRAkP+AJ9UZD52+BHhnskdwdgHJGvxZ44KbQCggAxl
+5K2gZS37iH60UpiLgumwIU=
=kJgm
-----END PGP SIGNATURE-----




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Shouldn't we be using openlog's LOG_NOWAIT option?
Next
From: Christopher Kings-Lynne
Date:
Subject: Re: Fixing pg_dump