Re: Does error within transaction imply restarting it?

Peter Eisentraut wrote:
>
> Haroldo Stenger writes:
>
> > I seems that other DBMSs, don't care about erroneous statements within
> > a transaction. Now, I have several paths to follow: 1) Hacking the
> > backend ;-)
>
> If you're really brave you can try this change in
> backend/tcop/postgres.c:
>
>         if (sigsetjmp(Warn_restart, 1) != 0)
>         {
>                 time(&tim);
>
>                 if (Verbose)
>                         TPRINTF(TRACE_VERBOSE, "AbortCurrentTransaction");
>
> -               AbortCurrentTransaction();
>                 InError = false;
>                 if (ExitAfterAbort)
>                 {
>                         ProcReleaseLocks(); /* Just to be sure... */
>                         proc_exit(0);
>                 }
>         }
>
> Absolutely no guarantee, there's probably more to it. Hmm, I wonder, maybe
> not.
>

It worked fine. I could do what I wanted, i.e. using GeneXus with
PostgreSQL. I'm happy. Thanks :)

> > How can I motivate key developers to make their way into an action
> > plan?
>
> Becoming one yourself or throwing large amounts of cash at the existing
> ones. :)

Maybe the former?

> Trying the above and tracing down any arising problems might be a
> start though.

Good enough.

A SET option, as Bruce sugested, would be great.