Re: [HACKERS] Possible issue with expanded object infrastructure onPostgres 9.6.1 - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] Possible issue with expanded object infrastructure onPostgres 9.6.1
Date
Msg-id CA+TgmoYGDR+z64Qx8wGro1SqnWYmQEvu4b_Ga5+ah+XaDmQNLg@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Possible issue with expanded object infrastructure on Postgres 9.6.1  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, Jan 19, 2017 at 9:39 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> If I had to bet on the basis of this much info, I would bet that the
> parallel-query infrastructure is dropping the ball somewhere and
> transmitting a corrupted datum that accidentally looks like it is
> an expanded-object reference.

There's code in datumSerialize() that is intended to do the right
thing with expanded-object references.  But it could have a bug, of
course.  That function gets called from SerializeParamList(), which
might be another place to look for problems if the crash can only be
reproduced when there are statement parameters.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] increasing the default WAL segment size
Next
From: Craig Ringer
Date:
Subject: Re: [HACKERS] Logical Replication WIP