| From: | Guo Xiang Tan <gxtan1990(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: BUG #15032: Segmentation fault when running a particular query |
| Date: | 2018-02-12 14:13:45 |
| Message-ID: | CAEL+R-CrBLW2bZPyzG-6zJQ7mdVOh1y+LDLzgkKHyqUy9LpQvA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi Tom,
We've upgraded to 10.2 and are not getting segmentation faults while
running the query anymore. Thank you for the fix.
On Sun, Jan 28, 2018 at 2:57 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I wrote:
> > I'll look into an actual fix tomorrow.
>
> I've pushed a fix for this. I concluded that there's no real reason
> to touch branches before 10: the index_markpos call is useless in the
> case in question, but it doesn't do any more than waste some cycles.
>
> regards, tom lane
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Scheffer | 2018-02-12 14:20:09 | Re: BUG #15060: Row in table not found when using pg function in an expression |
| Previous Message | Marko Tiikkaja | 2018-02-12 13:56:28 | Re: BUG #15060: Row in table not found when using pg function in an expression |