| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Getting server crash after running sqlsmith |
| Date: | 2017-03-29 00:57:51 |
| Message-ID: | CA+Tgmoav6Gs4Gg=418=dwNQ-iYEVEi1Lns5b302L=TLymftDmw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 28, 2017 at 2:36 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> tushar <tushar(dot)ahuja(at)enterprisedb(dot)com> writes:
>> After runinng sqlsmith against latest sources of PG v10 , able to see a
>> crash -
>
> 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.
/me blinks
Uh, what's insane about that? All it does is test a GUC (which is
surely parallel-safe) and call SendPostmasterSignal (which seems safe,
too).
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-03-29 00:59:17 | Re: [COMMITTERS] pgsql: Improve performance of find_all_inheritors() |
| Previous Message | Peter Eisentraut | 2017-03-29 00:57:34 | Re: make check-world output |