| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | scan-build plpython stuff |
| Date: | 2017-08-23 00:14:55 |
| Message-ID: | 57360908-3e89-4189-fe45-e9d0df288ce5@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wanted to make some progress cleaning up some of the warnings produced
by scan-build, so I grabbed plpython and fixed all the warnings there.
Attached are two patches, one that decorates PLy_elog() with compiler
hints similar to elog(), and one with some very minor tweaks. This
fixes all 13 or so (depending on scan-build version) warnings in plpython.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Add-compiler-hints-to-PLy_elog.patch | text/plain | 2.1 KB |
| 0002-PL-Python-Fix-remaining-scan-build-warnings.patch | text/plain | 1.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-08-23 00:28:15 | obsolete code in pg_upgrade |
| Previous Message | Andres Freund | 2017-08-22 23:41:23 | Re: POC: Sharing record typmods between backends |