Re: timestamp out of range while casting return value to function'sreturn type - Mailing list pgsql-general

From Karsten Hilbert
Subject Re: timestamp out of range while casting return value to function'sreturn type
Date
Msg-id 20190824100034.GA7766@hermes.hilbert.loc
Whole thread Raw
In response to timestamp out of range while casting return value to function'sreturn type  (Thiemo Kellner <thiemo@gelassene-pferde.biz>)
Responses Re: timestamp out of range while casting return value to function'sreturn type
List pgsql-general
On Sat, Aug 24, 2019 at 12:57:07AM +0000, Thiemo Kellner wrote:

> Call: select utils.get_max_timestamptz();
> --
>
> Function
> --
> create or replace function GET_MAX_TIMESTAMPTZ()
>   returns timestamptz
>   language plpgsql
>   immutable
>   -- Include the hosting schema into search_path so that dblink
>   -- can find the pglogger objects. There is no need to access
>   -- objects in other schematas not covered with public.
>   as
> $body$
>     begin
>         -- highest timestamps on 64bit lubuntu vanilla PostgreSQL 11.3
>         return '294277-01-01 00:59:59.999999'::timestamptz;
>     end;
> $body$;

Also, but that's a nitpick perhaps not relevant to your use case:

This

    $> psql -d gnumed_v22 -U <redacted>
    psql (11.5 (Debian 11.5-1+deb10u1))

    gnumed_v22=> select 'infinity'::timestamptz;
    -[ RECORD 1 ]---------
    timestamptz | infinity

    gnumed_v22=>

is the highest timestamp.

(You *can* count the horses in *your* corral but there's
 always more of them elsewhere ;-)

Just so you are aware.

Best,
Karsten
--
GPG  40BE 5B0E C98E 1713 AFA6  5BC0 3BEA AC80 7D4F C89B



pgsql-general by date:

Previous
From: PegoraroF10
Date:
Subject: Re: slow queries on system tables
Next
From: Thiemo Kellner
Date:
Subject: Re: timestamp out of range while casting return value to function'sreturn type