Investigate why test_psycopg2 is failing with "UndefinedColumn" instead of "ProgrammingError"

[chanchiem]

The test for some reason now is failing. This is aside from any recent changes that we've made.

...
        exception = subsegment.cause['exceptions'][0]
>       assert exception.type == 'ProgrammingError'
E       AssertionError: assert 'UndefinedColumn' == 'ProgrammingError'
E         - UndefinedColumn
E         + ProgrammingError
tests/ext/psycopg2/test_psycopg2.py:147: AssertionError
...

We re-ran the test for a build that had previously worked and now it appears to be failing. This issue is made to investigate this and will be updated when further information is found.

Please refer to this link for the build re-run of a previously passing build.

[chanchiem]

In version 2.8.0 of Psycopg2, they announced the following:
Added errors module. Every PostgreSQL error is converted into a specific exception class (ticket #682).

This means that they added granular error exception classes, so the exception that we originally tested for (ProgrammingError) is now a base class exception for what was previously tested. In particular, the test that we originally wrote tested for a bad query whose database column doesn't exist, hence why we are now seeing UndefinedColumn exceptions. The UndefinedColumn class is inherited from the ProgrammingError class.

Here is a list of all the mappings from the base classes.

This seems to be only an issue with the test. Psycopg2 seems to function fine when instrumented with X-Ray

[chanchiem]

Merged