Re: patch for 9.2: enhanced errors - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: patch for 9.2: enhanced errors
Date
Msg-id 4E245BB6020000250003F48D@gw.wicourts.gov
Whole thread Raw
In response to Re: patch for 9.2: enhanced errors  (Josh Berkus <josh@agliodbs.com>)
Responses Re: patch for 9.2: enhanced errors
List pgsql-hackers
Josh Berkus <josh@agliodbs.com> wrote:
> I'm less concerned about the standard here and more concerned
> about what helps our users.  Having column names for an FK error
> is *extremely* useful for troubleshooting, particularly if the
> database has been upgraded from the 7.4 days and has non-useful FK
> names like "$3".
If it gives a FK constraint name, isn't there a way to get from that
to the columns used by the constraint?  If we want to support
something non-standard, we can always tell them to look at the text
of the error detail, right?
-Kevin


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Commitfest Status: Sudden Death Overtime
Next
From: Robert Haas
Date:
Subject: Re: Commitfest Status: Sudden Death Overtime