Update docs to use postgres + psycopg in order to avoid known issues with psycopg2

[sfc-gh-gtokernliang]

Description

#1685 raises a known issue where SQLalchemy postgres + psycopg2 has issues due to psycopg2 not converting np floats to a storable format by default - see sqlalchemy/sqlalchemy#11712. This is fixed out of the box with psycopg >= 3.2 (and demonstrated to be working in #1685), so this PR aims to update the docs to guide users down this smoother path instead.

Other details good to know for developers

It doesn't look like we're directly depending on psycopg2, so no package updates were made

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to
  not work as expected)
• New Tests
• This change includes re-generated golden test results
• This change requires a documentation update

---

Important

Update documentation and tests to use psycopg for PostgreSQL connections, replacing psycopg2.

• Documentation:
  • Update PostgreSQL connection examples to use psycopg instead of psycopg2 in release_blog_1dot.md and index.md.
  • Modify example connection strings to postgresql+psycopg:// format.
• Tests:
  • Update test database connection string to use psycopg in test_database.py.

^{This description was created by for a926618. It will automatically update as commits are pushed.}

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB