| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | tushar <tushar(dot)ahuja(at)enterprisedb(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Getting server crash after running sqlsmith |
| Date: | 2017-05-23 12:55:58 |
| Message-ID: | CA+TgmoZJ_bM2P=6cLphb6q=3pNj6cBZcCNgok5qfvV52og_YJg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, May 23, 2017 at 1:46 AM, tushar <tushar(dot)ahuja(at)enterprisedb(dot)com> wrote:
> On 03/29/2017 12:06 AM, Tom Lane wrote:
>>
>> Hm ... I don't see a crash here, but I wonder whether you have parameters
>> set that would cause this query to be run as a parallel query? Because
>> pg_rotate_logfile() is marked as parallel-safe in pg_proc, which seems
>> probably insane.
>
> Well, I am able to see a crash . Enable "logging_collector=on" in
> postgresql.conf file / restart the server and fire below sql query - 5 or 6
> times
Just out of curiosity, what happens if you try it with the attached patch?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| Attachment | Content-Type | Size |
|---|---|---|
| no-sigmask.patch | application/octet-stream | 579 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | tushar | 2017-05-23 13:07:40 | Re: Getting server crash after running sqlsmith |
| Previous Message | Mahi Gurram | 2017-05-23 12:22:33 | Re: Regarding Postgres Dynamic Shared Memory (DSA) |