MIME-Version: 1.0
From: Durgamahesh Manne <maheshpostgres9@gmail.com>
Date: Wed, 22 May 2024 14:56:26 +0530
Message-ID: <CAJCZkoJQ9n1o_+1CWAE2gNtSdWxU_MM460dr3Gq69jZr43e_+w@mail.gmail.com>
Subject: Regarding use case of epoch to generate nanoseconds precision
To: pgsql-general@lists.postgresql.org
Cc: "keith.fiske@crunchydata.com" <keith.fiske@crunchydata.com>
Content-Type: multipart/alternative; boundary="000000000000ebd5540619077564"
Archived-At: <https://www.postgresql.org/message-id/CAJCZkoJQ9n1o_%2B1CWAE2gNtSdWxU_MM460dr3Gq69jZr43e_%2Bw%40mail.gmail.com>
Precedence: bulk

--000000000000ebd5540619077564
Content-Type: text/plain; charset="UTF-8"

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 =>   (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, but
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.


Regards,
Durga Mahesh Manne

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

<div dir=3D"ltr">Hi=C2=A0=C2=A0<div><br></div><div>Postgres supports only u=
pto microseconds (6 decimal precision).</div><div>How do we generate timest=
amp with nanoseconds as rds postgres not supported=C2=A0timestamp9 extensio=
n ?</div><div>Is there a way to generate timestamp with nanoseconds precisi=
on on pg_partman with epoch without typecasting or with 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><br></div><div>Regards,</div><div>Durga=
 Mahesh Manne</div><div><br></div><div><br></div><div><br></div><div><br></=
div><div><br><div><div><br></div><div><br></div></div></div></div>

--000000000000ebd5540619077564--