Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

Hi - what is the status of this issue and a solution (for postgres)?  It's a business impacting issue for our company and we'll need to replace airbyte with another solution within the next couple of weeks without a target date for a fix.

<https://github.com/airbytehq/airbyte/issues/8280>

<@U02DFTJ4V3J> can you give your opinion here? :smile:

<@U01MMSDJGC9> currently we are working on solution for MySQL, so we can work on the solution for Postgres during this sprint, will create a separate ticket to track the activity 

<@U02DFTJ4V3J> - is that a (2) week sprint?

cc: <@U02NXFLRYLR> fyi

<@U02NC955LRL> yes, I will let you know as soon as we get any results 

good morning <@U02DFTJ4V3J>!  any updates on this issue?

good morning <@U02NXFLRYLR>
we finished with a research and posted updates to the comment <https://github.com/airbytehq/airbyte/issues/9337#issuecomment-1023203660>
right now we are working on the issue <https://github.com/airbytehq/airbyte/issues/7944> extending airbyte JSONSchema to pass additional parameters that will indicate whether timestamp/time timezone aware or not

this will allow to create correct data-type on the destination side

could you possibly describe what is your business case?
cc <@U02NC955LRL>

Okay, thanks for the update <@U02DFTJ4V3J>.  Our business case is that we use a postgres instance as our transaction system and timezones are important.  When replicating that transaction data into Snowflake we essentially lose fidelity because of this issue.  Running the same query in both environment yields different results when sorting/ranking by timestamp-timezone.

<@U02NXFLRYLR> could you possibly share a few examples of the sorting results from Postgres and Snowflake?

<@U02DFTJ4V3J> Here is an example where we are trying to rank `category_id` by the max `updated_at` column.  The 1st screenshot is the source(postgres) and the 2nd screenshot is the target(snowflake).  You'll notice that on the target, the timezone info has been truncated and the same ranking query returns the records in a completely different order.

I see, it’s a different issue <https://github.com/airbytehq/airbyte/issues/8904>
<@U02U115DYMP> can we prioritise the fix for Postgres to the current sprint?
cc <@U02TFM12THU>

<@U02DFTJ4V3J> any progress to share on this issue?

hi <@U02NXFLRYLR>
the fix is under Airbyte review <https://github.com/airbytehq/airbyte/pull/10242>
cc <@U02TKE11269> <@U02UC3SNJ72>