Postgres: The Batteries Included Database
info.crunchydata.com
info.crunchydata.com
I don't know of an existing nanosecond-precision timestamptz type, but it's not that much of a lift to create one yourself. I've muddled through C a couple of times to do so. Often I pick an existing extension that's similar to what I want to do, and modify it.
And if Rust is more to your liking, there's a toolkit for building extensions in Rust as well: https://github.com/zombodb/pgx
A drawback of using custom extensions is you're often limited to then managing your own PostgreSQL installation as most PostgreSQL SaaS offerings don't support installation of third-party C extensions. If nanosecond precision is a core aspect of your work, then it may very well be worth the effort.
Another option is to store nanoseconds in an additional integer column. If you want, you can create a composite type (https://www.postgresql.org/docs/13/rowtypes.html) of timestamptz and integer, which might make things more manageable (or less, depending on your PostgreSQL driver support for composite types). This allows you to use stock PostgreSQL while you handle the data stitching in your application.
Other than that, thank you very much.
Choosing any of these options is more likely to actually solve your issue.