Re: BUG #14876: Segmentation fault with JSONB column used in store proc that gets used by view and later altered
Michael Paquier <michael.paquier@gmail.com>
From: Michael Paquier <michael.paquier@gmail.com>
To: samuel.horwitz@gmail.com
Cc: PostgreSQL mailing lists <pgsql-bugs@postgresql.org>
Date: 2017-10-26T19:24:06Z
Lists: pgsql-bugs
Attachments
- initial.sql (application/octet-stream)
- fix-it.sql (application/octet-stream)
- break-it.sql (application/octet-stream)
On Thu, Oct 26, 2017 at 11:40 AM, <samuel.horwitz@gmail.com> wrote: > I have created a public Gist with reproduction steps and dumps, attached > here: > https://gist.github.com/samuelhorwitz/0bc77a517238914512fc8cdf50d217cd > > Please scroll to the bottom (or click here > https://gist.github.com/samuelhorwitz/0bc77a517238914512fc8cdf50d217cd#gistcomment-2240442) > to see my steps. I haven't looked at this thing in details. But this data may not be present forever, say github.com is down or is removed from existence. So if you can, please always attach any self-contained test case in a way that it is saved in the archives of postgresql.org. In this case, that would have been to email directly pgsql-bugs instead of using the website form. psql -f initial.sql # This works psql -c 'SELECT id, json FROM base_table_json' psql -f break-it.sql # this breaks psql -c 'SELECT id, json FROM base_table_json' psql -f fix-it.sql # this works psql -c 'SELECT id, json FROM base_table_json' This reminds me of this case: https://www.postgresql.org/message-id/20150707165212.1188.60819@wrigleys.postgresql.org. The backtrace is not exactly the same, but that's really close. -- Michael
Commits
-
Fix crash when columns have been added to the end of a view.
- d5b760ecb5e1 11.0 landed
- ddde3b4f3e88 10.1 landed
- acd3287e437e 9.5.10 landed
- 9d15b8b36a91 9.3.20 landed
- 80e79718d0ea 9.2.24 landed
- 7e5e8b36d478 9.6.6 landed
- 66104119e1fb 9.4.15 landed