Inserting now() at time zone 'utc' gives invalid results about node-postgres HOT 4 CLOSED

now() at time zone 'utc' converts the timestamptz to a plain timestamp (without time zone), which is then interpreted as being in the connection’s time zone whenever it’s cast back to timestamptz.

PS Because everywhere I saw was recommendation: Always use timestamp field with utc timezone or just some other timezone.

Well, that recommendation is backwards. You should almost always use timestamptz (which unambiguously represents a moment in time, the usual datetime complexities notwithstanding), and almost never timestamp (which doesn’t represent anything in particular without context and is easy to misuse by accident, as seen here).

from node-postgres.

Fixed by setting DB default timezone:
ALTER DATABASE [database_name] SET TIMEZONE='UTC';

from node-postgres.

You want just DEFAULT now(). now() is already a timestamptz.

from node-postgres.

But why now() that already contains timezone differs from now() at time zone 'utc'? I was assuming that there might be some database connection configuration like useUTC: true, but I didn't find any. So it seems like same query provides different result, depending on db client time zone even when there are no timestamp or time zone explicitly defined in the query.

PS Because everywhere I saw was recommendation: Always use timestamp field with utc timezone or just some other timezone.

from node-postgres.