From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: pgsql-hackers@postgreSQL.org
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Upgrading the backend's error-message infrastructure
Date: Fri, 14 Mar 2003 23:48:10 -0500
Message-ID: <26429.1047703690@sss.pgh.pa.us> (raw)
In-Reply-To: <25281.1047690137@sss.pgh.pa.us>
References: <Pine.LNX.4.44.0303132349500.1617-100000@peter.localdomain>
<25281.1047690137@sss.pgh.pa.us>
I said:
> I had missed the relevance of <condition information item name>, will
> go look at it.
It looks to me like support of the SQL condition information items would
require adding about two dozen optional fields to my spec for the Error
protocol message, and the same number of optional errFOO(...)
subroutines in the ereport() interface (only two or three of which would
be likely to get invoked in any one ereport instance). This is a bit
more than I'd been visualizing, but AFAICS the proposed mechanisms would
work perfectly well with it. I won't bore the list with a detailed spec
for the individual items --- they seem pretty obvious.
Given that we now need order-of-thirty possible field types, do you feel
uncomfortable with a single-byte field identifier in the FE/BE protocol?
I'm still leaning that way on the grounds of compactness and programming
simplicity, but I can see where someone might want to argue it won't do
in the long run.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, peter_e@gmx.net, pgsql-hackers@postgreSQL.org
Subject: Re: [INTERFACES] Upgrading the backend's error-message infrastructure
In-Reply-To: <26429.1047703690@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox