Merge pull request #5578 from segmentio/dineshraj-arunmozhi-patch-1

Update postgres-setup.md

Author: forstisabella

src/connections/reverse-etl/reverse-etl-source-setup-guides/postgres-setup.md

@@ -6,6 +6,13 @@ Set up Postgres as your Reverse ETL source.
 
 At a high level, when you set up Postgres for Reverse ETL, the configured user/role needs read permissions for any resources (databases, schemas, tables) the query needs to access. Segment keeps track of changes to your query results with a managed schema (`__SEGMENT_REVERSE_ETL`), which requires the configured user to allow write permissions for that schema.
 
+Segment supports the following Postgres database providers:
+- Heroku
+- RDS
+
+> warning ""
+> Segment only supports these Postgres database providers. Postgres databases from other providers aren't guaranteed to work. For questions or concerns about Segment-supported Postgres providers, [contact Segment Support](https://segment.com/help/contact){:target="_blank"}.
+
 ## Set up guide
 To set up Postgres with Reverse ETL:
 
@@ -28,4 +35,4 @@ To set up Postgres with Reverse ETL:
 ## Extra permissions
 * Give the `segment` user read permissions for any resources (databases, schemas, tables) the query needs to access. 
 
-* Give the `segment` user write permissions for the Segment managed schema (`__SEGMENT_REVERSE_ETL`), which keeps track of changes to the query results.  
+* Give the `segment` user write permissions for the Segment managed schema (`__SEGMENT_REVERSE_ETL`), which keeps track of changes to the query results.