| From: | John Naylor <jcnaylor(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | lingering references to V0 calling convention |
| Date: | 2018-04-23 11:17:59 |
| Message-ID: | CAJVSVGVydmhLBdm80Rw3G8Oq5TnA7eCxUv065yoZfNfLbF1tzA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I noticed one in the SPI docs and tried to look for more. The attached
patch is an attempt at removing the remaining references. The original
SPI example returned a uint64 as a signed int8 SQL type, so I'm not
sure if I handled that correctly.
However, I didn't touch the documentation of the configure options for
--disable-floatN-byval, since this thread proposed something a bit
more invasive:
-John Naylor
| Attachment | Content-Type | Size |
|---|---|---|
| remove-v0-from-docs.patch | text/x-patch | 2.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2018-04-23 11:25:09 | Re: minor fix for acquire_inherited_sample_rows |
| Previous Message | Heikki Linnakangas | 2018-04-23 10:22:21 | Re: wal_consistency_checking reports an inconsistency on master branch |