| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | mrechte(at)gmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: 37.10.3 |
| Date: | 2020-03-13 16:22:16 |
| Message-ID: | 28597.1584116536@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> writes:
> On Thu, 2020-03-12 at 06:34 +0000, PG Doc comments form wrote:
>> There is mention to macro PG_ARGNULL_xxx() which I cannot locate. Aren't you
>> talking of PG_ARGISNULL(n) ?
> Indeed.
Indeed :-(.
> Here is a patch for that.
Not quite right, it's just PG_ARGISNULL without any type-specific
decoration. Will push in a moment.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2020-03-13 22:56:37 | Re: Wrong insert before trigger examples |
| Previous Message | Silvan Jegen | 2020-03-13 07:32:15 | Re: Move description of general lock behaviour out of the "13.3.1. Table-level Locks section" |