I'm baffled by the insistence that "users" (backend services, really) should avoid timestamp in favor of timestampz.<p>I literally DO NOT understand, how is this good advice.<p>My backend service exists in some abstraction of a Linux environment, with a fixed timezone, most commonly UTC.
It maintains a pool of connections to Postgres, all sharing the same Postgres user, and the same timezone.<p>Why on earth would I prefer a timestampz to timestamp? Why would I even involve the server timezone into this equation?<p>I want to store timestamps in a uniform way, I store them in UTC as timestamps. If I stored them in a timestampz column, if the server timezone were to adjust, I'd get literally different values.<p>If I want to store timezone values per user (of my service), or per operation (that my users perform), then again, surely I have to handle that users move and change their timezones. Again, how does timestampz with its reliance on the connection timezone serve me?