| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Geoghegan <pg(at)heroku(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Possible issue with expanded object infrastructure on Postgres 9.6.1 |
| Date: | 2017-01-20 19:56:47 |
| Message-ID: | CA+TgmoYGDR+z64Qx8wGro1SqnWYmQEvu4b_Ga5+ah+XaDmQNLg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jan 19, 2017 at 9:39 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2017-01-20 19:57:10 | Re: Logical Replication WIP |
| Previous Message | Robert Haas | 2017-01-20 19:50:05 | Re: increasing the default WAL segment size |