Re: Problem with aborting entire transactions on error

From: Zbigniew <zbigniew2011(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Problem with aborting entire transactions on error
Date: 2012-12-11 11:26:43
Message-ID: CALT7RM-vHPLFWh6qrThfsghO0GS94JbfNRn7tj8rHeuguLHg3g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2012/12/10, Kevin Grittner <kgrittn(at)mail(dot)com>:

> Could an option like this be added to the server? Probably. Has
> anyone worked on such a feature? Not that I know of. Would such a
> feature be accepted if written? I think a better case would need to
> be made for its value compared to the added code complexity and
> maintenance burden than has been made so far. Since this is
> primarily of interest for bulk loads and interactive work, and
> there are already solutions for both of those, it would probably be
> seen as not worth its weight.

Thanks for detailed explanation. From what I see, it's rather not
going to happen.

> It's only by careful gatekeeping that the source code has been kept
> manageable. A quick count shows that there are 1,167,732 lines of
> code, counting only *.c and *.h files. Every added line has a
> maintenance cost.

I agree - but, on the other hand, every added line of code in the
software of the users (programmers using PG) has its maintenance cost
too. And it has to be multiplied by the number of the users, then
again: by the number of the users of their software...
--
regards,
Zbigniew

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Zbigniew 2012-12-11 11:28:33 Re: Problem with aborting entire transactions on error
Previous Message Pavel Stehule 2012-12-11 11:00:21 Re: Bug in GET STACKED DIAGNOSTICS ?