Date / Time

Always use timestamptz, never bare timestamp

timestamp8 bytes

Only when timezone is truly irrelevant (e.g., abstract schedule templates).

Range

4713 BC to 294276 AD

Performance

Same as timestamptz.

Comparison

timestamp (without time zone) does not track timezone info. If your server moves or your app goes global, timestamps become ambiguous. Use timestamptz unless you have a specific reason not to.

SQL Example

CREATE TABLE schedule_templates (
  id bigint GENERATED ALWAYS AS IDENTITY PRIMARY KEY,
  start_time timestamp NOT NULL
);