| From: | Steve Singer <steve(at)ssinger(dot)info> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PG 12 beta 1 segfault during analyze |
| Date: | 2019-06-18 01:46:02 |
| Message-ID: | cabaff56-3da9-2e8a-a254-7d1786e13264@ssinger.info |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/15/19 10:18 PM, Tom Lane wrote:
> Steve Singer <steve(at)ssinger(dot)info> writes:
>> I encountered the following segfault when running against a PG 12 beta1
>> during a analyze against a table.
> Nobody else has reported this, so you're going to have to work on
> producing a self-contained test case, or else debugging it yourself.
>
> regards, tom lane
>
>
>
The attached patch fixes the issue.
Steve
| Attachment | Content-Type | Size |
|---|---|---|
| heapam_handler.c.diff | text/x-patch | 627 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2019-06-18 03:30:38 | Re: idea: log_statement_sample_rate - bottom limit for sampling |
| Previous Message | Michael Paquier | 2019-06-18 00:59:08 | Re: Race conditions with TAP test for syncrep |