| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Konstantin Izmailov <pgfizm(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PQprepare in PostgreSQL 7.4 (lack of SAVEPOINTs) |
| Date: | 2010-06-24 03:25:44 |
| Message-ID: | AANLkTil1a-iaTPSvEX1aZYIKYjCSAQ8o_ZIg8SetMS3K@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Jun 23, 2010 at 10:55 PM, Konstantin Izmailov <pgfizm(at)gmail(dot)com> wrote:
> Is there a way to prevent transaction abort when preparing command in
> version 7.4?
>
> I googled but haven't been able to find the answer. The issue occurs when
> our software trys to prepare a command that is already prepared (by the same
> or different app). PQprepare returns error and aborts current transaction.
> The company is not willing to upgrade from 7.4 to a later version due to
> risk.
>
> SAVEPOINTs are not available in v.7.4. I'm looking at PQdescribePrepared
> function. What is the right solution?
Upgrading to a later version of pgsql, or don't issue that command
twice in a transaction.
The risk of upgrading is less than the risk of staying on an
unsupported version of pgsql. The company that won't upgrade is
making a poorly informed decision.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2010-06-24 03:29:48 | Re: copy/duplicate database schemas |
| Previous Message | Konstantin Izmailov | 2010-06-24 02:55:32 | PQprepare in PostgreSQL 7.4 (lack of SAVEPOINTs) |