Regarding use case of epoch to generate nanoseconds precision

From: Durgamahesh Manne <maheshpostgres9(at)gmail(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Cc: "keith(dot)fiske(at)crunchydata(dot)com" <keith(dot)fiske(at)crunchydata(dot)com>
Subject: Regarding use case of epoch to generate nanoseconds precision
Date: 2024-05-22 09:26:26
Message-ID: CAJCZkoJQ9n1o_+1CWAE2gNtSdWxU_MM460dr3Gq69jZr43e_+w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message XChy 2024-05-22 09:27:44 Missed compiler optimization issue in function select_rtable_names_for_explain
Previous Message HORDER Philip 2024-05-22 08:33:39 Re: Restore of a reference database kills the auto analyze processing.