Thread

  1. reproducible 9.5: ERROR: requested object address for unsupported object class 32: ...

    Josh Kupershmidt <schmiddy@gmail.com> — 2015-06-05T00:40:44Z

    Hi all,
    
    Attached is a small testcase which should produce an ERROR like:
    
    ERROR:  requested object address for unsupported object class 32: text
    result "unrecognized object 3576 112581 0"
    
    Tested on git master.
    
    Some further tidbits: object class 32 corresponds to OCLASS_TRANSFORM
    by my reckoning, which lines up with the ERROR happening during
    dropping the  hstore_plpython2u extension, which contains some
    transforms.
    
    I happened upon this case by digging around in the event trigger
    handling of transforms after perusing the scan-build complaint[1]
    about the T_CreateTransformStmt case on line 1440 of
    src/backend/tcop/utility.c neglecting to set 'address', then passing
    that struct on to EventTriggerCollectSimpleCommand. Not sure if that's
    precisely related to what's happening here, since the error here seems
    to only happen during the DROP EXTENSION, not CREATE, but that area of
    the code sure smells funny to me.
    
    Josh
    
    [1] http://pgci.eisentraut.org/jenkins/view/PostgreSQL/job/postgresql_master_scan-build/2285/clangScanBuildBugs/browse/report-GQoirj.html#EndPath
    
  2. Re: reproducible 9.5: ERROR: requested object address for unsupported object class 32: ...

    Josh Kupershmidt <schmiddy@gmail.com> — 2015-06-05T01:28:56Z

    On Thu, Jun 4, 2015 at 8:40 PM, Josh Kupershmidt <schmiddy@gmail.com> wrote:
    > Hi all,
    >
    > Attached is a small testcase which should produce an ERROR like:
    >
    > ERROR:  requested object address for unsupported object class 32: text
    > result "unrecognized object 3576 112581 0"
    
    Wow, I just noticed that Michael Paquier recently stumbled onto the
    same problem and already has a fix. FWIW, the patch in:
    
    http://www.postgresql.org/message-id/CAB7nPqT2SZ39N_wH+WK8JGPKO3LCyWQiLoxgcgq_UyPJNc8hSg@mail.gmail.com
    
    seems to fix the error for me. Sorry for the noise.
    
    Josh