Re: [HACKERS] pg_stat_get_progress_info(NULL) blows up

2016-03-14 Thread Tom Lane
Thomas Munro writes: > I guess pg_stat_get_progress_info should either be strict (see > attached) or check for NULL. Pushed, thanks. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes

Re: [HACKERS] pg_stat_get_progress_info(NULL) blows up

2016-03-13 Thread Amit Langote
On 2016/03/14 10:54, Thomas Munro wrote: > Hi > > I guess pg_stat_get_progress_info should either be strict (see > attached) or check for NULL. Thanks a lot for reporting and the patch. I think that's an oversight. Thanks, Amit -- Sent via pgsql-hackers mailing list

[HACKERS] pg_stat_get_progress_info(NULL) blows up

2016-03-13 Thread Thomas Munro
Hi I guess pg_stat_get_progress_info should either be strict (see attached) or check for NULL. -- Thomas Munro http://www.enterprisedb.com pg_stat_get_progress_info-strict.patch Description: Binary data -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to