On Wed, Jan 18, 2017 at 7:36 AM, Karl O. Pinc <k...@meme.com> wrote:
> Maybe. It's not user-supplied data that's corrupted but it is
> PG generated data which is generated for and supplied to the user.
> I just looked at all uses of XX001 and it is true that they all
> involve corruption of user-supplied data.
> If you don't want to use XX001 use XX000. It does not seem worth
> making a new error code for just this one case.
Our ideas rather map here, ERRCODE_INTERNAL_ERROR would be adapted for
this situation. Do any of you want to give it a shot or should I?
Sent via pgsql-hackers mailing list (email@example.com)
To make changes to your subscription: