Timestamptz conversion possible issue?

[avilaton]

Hi,

we synched a few tables and ran an analytic query much faster with bemidb but we are seeing some discrepancies in our timestamp with timezone things. I'm not quite sure where the issue might be or if it should be that I need to start bemidb with a parameter that I might have missed.
Our table has a created column of the form

CREATE TABLE something (
   created timestamp with time zone NOT NULL,
   id INTEGER PRIMARY KEY,
   ...

and selecting form postgres we see this

select
  created,
  created at time zone 'America/Los_Angeles' as other_created,
  id
from something where flow_number=1119016;

and we get this in postgresql

            created            |          timezone          | id
-------------------------------+----------------------------+-------------
 2025-02-26 22:42:18.537575+00 | 2025-02-26 14:42:18.537575 |     1119016
(1 row)

in bemidb

          created           |             timezone             | id
----------------------------+----------------------------------+-------------
 2025-02-26 22:42:18.537575 | 2025-02-27 06:42:18.537575+00:00 |     1119016
(1 row)

clearly something funky is going on

• created has +00 in postgresq, but looks naive in bemidb
• timezone (the column that is shifted) is naive in postgresql, but looks as a timestamptz in bemidb.

Any tips on what we might be doing wrong here?
Thanks!!!!