From: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
---|---|
To: | jian he <jian(dot)universality(at)gmail(dot)com> |
Cc: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Joseph Koshakow <koshy44(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Gregory Stark (as CFM)" <stark(dot)cfm(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Infinite Interval |
Date: | 2023-09-22 10:12:53 |
Message-ID: | CAExHW5v+obHpBFCx8wDkYMRzjiHVeSGoeXXvReNQMhw--63hJA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Sep 22, 2023 at 2:35 PM jian he <jian(dot)universality(at)gmail(dot)com> wrote:
>
> /* TODO: Handle NULL inputs? */
> since interval_avg_serialize is strict, so handle null would be like:
> if (PG_ARGISNULL(0)) then PG_RETURN_NULL();
That's automatically taken care of by the executor. Functions need to
handle NULL inputs if they are *not* strict.
#select proisstrict from pg_proc where proname = 'interval_avg_serialize';
proisstrict
-------------
t
(1 row)
#select proisstrict from pg_proc where proname = 'interval_avg_deserialize';
proisstrict
-------------
t
(1 row)
--
Best Wishes,
Ashutosh Bapat
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2023-09-22 10:18:43 | Re: Synchronizing slots from primary to standby |
Previous Message | Tatsuo Ishii | 2023-09-22 10:12:50 | Re: Row pattern recognition |