about error handling mechanism - Mailing list pgsql-hackers

From fanng yuan
Subject about error handling mechanism
Date
Msg-id AANLkTikBjKuM9geRbwS_TbN44BzF-Pyrs9EBxHJ=MhLx@mail.gmail.com
Whole thread Raw
Responses Re: about error handling mechanism  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
Hi!
I was looking into the postgres error handling mechanism, and the
documentation states that the present mechanism is primitive.

I quote "whenever the parser, planner/optimizer or executor decide that a
statement cannot be processed any longer,
the whole transaction gets aborted and the system jumps back into the main
loop to get the next command from the client application."

Also, it states " it is possible that the database server is in an
inconsistent state at this point so returning to the upper executor or
issuing
more commands might corrupt the whole database"

Since postgres aborts the transaction compeletely, why would it be ever
left in an inconsistant state in such an event?

Also , I want to get someone's help about the mechanism about how it works.
Could someone help me?

thanks


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Re: Proposed Windows-specific change: Enable crash dumps (like core files)
Next
From: Pavel Stehule
Date:
Subject: patch: remove redundant code from pl_exec.c