From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Haroldo Stenger <hstenger(at)adinet(dot)com(dot)uy> |
Cc: | Ed Loehr <eloehr(at)austin(dot)rr(dot)com>, postgres general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Does error within transaction imply restarting it? |
Date: | 2000-04-15 18:52:02 |
Message-ID: | Pine.LNX.4.21.0004151642160.523-100000@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
> 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. :) Trying the above and tracing down any arising problems might be a
start though.
--
Peter Eisentraut Sernanders väg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-04-15 19:54:37 | Re: Does error within transaction imply restarting it? |
Previous Message | Stephen J Lombardo | 2000-04-15 18:03:23 | Re: Postgresqlism & Vacuum? |