I have pull the postgres destination connector and push to store in my private registry but it did not support the normalized transformation as the image that I have pull. I pulled it without change or add anything. @kapa.ai

Based on the information provided in the knowledge sources, it appears that normalization for the Postgres destination connector has been deprecated in recent versions of Airbyte. This explains why you're not seeing support for normalized transformations in the image you pulled. According to a comment by an Airbyte team member in [this GitHub issue](https://github.com/airbytehq/airbyte/issues/32288): "Postgres was migrated to typing-deduping method deprecating the normalization. Please upgrade to latest version of the connector and try to sync the data again." This indicates that Airbyte has moved away from the previous normalization approach for Postgres in favor of a new method called "typing-deduping". Additionally, in [another GitHub issue](https://github.com/airbytehq/airbyte/issues/7229), an Airbyte team member stated: "Normalization is deprecated and will be removed from the codebase soon." This further confirms that normalization, as it was previously implemented, is being phased out across Airbyte connectors. If you need to perform transformations on your data after it's loaded into Postgres, Airbyte now recommends using dbt with an orchestrator to run post-sync transformations, as mentioned in [this GitHub discussion](https://github.com/airbytehq/airbyte/discussions/38168): "If you need to use post-transformations to your data Airbyte recommend to use dbt with an orchestrator to run the job to your pipeline." In summary, the lack of normalization support in the Postgres destination connector you pulled is expected behavior in recent versions of Airbyte, as they have moved away from this feature in favor of other approaches.