MIME-Version: 1.0
References: <CAJCZkoJQ9n1o_+1CWAE2gNtSdWxU_MM460dr3Gq69jZr43e_+w@mail.gmail.com>
In-Reply-To: <CAJCZkoJQ9n1o_+1CWAE2gNtSdWxU_MM460dr3Gq69jZr43e_+w@mail.gmail.com>
From: o1bigtenor <o1bigtenor@gmail.com>
Date: Wed, 22 May 2024 05:53:02 -0500
Message-ID: <CAPpdf58BB55co4F9YUTs_dTfMpJoY-=4GFqT=YE+5uXc22M1HQ@mail.gmail.com>
Subject: Re: Regarding use case of epoch to generate nanoseconds precision
Cc: pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="0000000000003b8433061908bf51"
Archived-At: <https://www.postgresql.org/message-id/CAPpdf58BB55co4F9YUTs_dTfMpJoY-%3D4GFqT%3DYE%2B5uXc22M1HQ%40mail.gmail.com>
Precedence: bulk

--0000000000003b8433061908bf51
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, May 22, 2024 at 4:21=E2=80=AFAM Durgamahesh Manne <maheshpostgres9@=
gmail.com>
wrote:

> Hi
>
> Postgres supports only upto microseconds (6 decimal precision).
> How do we generate timestamp with nanoseconds as rds postgres not
> supported timestamp9 extension ?
> Is there a way to generate timestamp with nanoseconds precision on
> pg_partman with epoch without typecasting or with typecasting  ?
>
> p_epoch =3D>   (to_timestamp(control column))
> Here what is the control column?
> How to run it with the create_parent function of partman?
>
> Here as per the pg_partman doc
> p_epoch - tells pg_partman that the control column is an integer type, bu=
t
> actually represents an epoch time value. Valid values for this option are=
:
> 'seconds', 'milliseconds', 'nanoseconds', and 'none'. The default is
> 'none'. All table names will be time-based. In addition to a normal index
> on the control column, be sure you create a functional, time-based index =
on
> the control column (to_timestamp(control column)) as well so this works
> efficiently.
>
>
Not a postgresql expert but - - - I'm wondering how you actually plan to
implement this nanosecond timestamp?
You will be working in an area where you will need some extreme corner case
equipment for all items in the system.
Not saying that measurements in this area can't be done rather that you
will have internal ambiguities in your
accuracy (network timing for one at the very least).

Good luck

--0000000000003b8433061908bf51
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Wed, May 22, 2024 at 4:21=E2=80=AF=
AM Durgamahesh Manne &lt;<a href=3D"mailto:maheshpostgres9@gmail.com">mahes=
hpostgres9@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex"><div dir=3D"ltr">Hi=C2=A0=C2=A0<div><br></div><div>Post=
gres supports only upto microseconds (6 decimal precision).</div><div>How d=
o we generate timestamp with nanoseconds as rds postgres not supported=C2=
=A0timestamp9 extension ?</div><div>Is there a way to generate timestamp wi=
th nanoseconds precision on pg_partman with epoch without typecasting or wi=
th typecasting=C2=A0 ?</div><div><br></div><div>p_epoch =3D&gt;=C2=A0=C2=A0

(to_timestamp(control column))

</div><div>Here what is the control column?<br></div><div>How to run it wit=
h the create_parent function of partman?</div><div><br></div><div>Here as p=
er the pg_partman doc=C2=A0</div><div>p_epoch - tells pg_partman that the c=
ontrol column is an integer type, but actually represents an epoch time val=
ue. Valid values for this option are: &#39;seconds&#39;, &#39;milliseconds&=
#39;, &#39;nanoseconds&#39;, and &#39;none&#39;. The default is &#39;none&#=
39;. All table names will be time-based. In addition to a normal index on t=
he control column, be sure you create a functional, time-based index on the=
 control column (to_timestamp(control column)) as well so this works effici=
ently.<br></div><div><br></div></div></blockquote><div><br></div><div>Not a=
 postgresql expert but - - - I&#39;m wondering how you actually plan to imp=
lement this nanosecond timestamp?</div><div>You will be working in an area =
where you will need some extreme corner case equipment for all items in the=
 system. <br></div><div>Not saying that measurements in this area can&#39;t=
 be done rather that you will have internal ambiguities in your <br></div><=
div>accuracy (network timing for one at the very least). <br></div><div><br=
></div><div>Good luck</div><div><br></div></div></div>

--0000000000003b8433061908bf51--