docs: Replace psycopg2 URLs

Author: jpmckinney

docs/python/style_guide.rst

@@ -216,11 +216,11 @@ Maintenance
 
 Maintainers can find improper formatting with these regular expressions. Test directories and Sphinx ``conf.py`` files can be ignored, if needed.
 
--  Unnamed placeholders, except for log messages, ``strftime()``, `psycopg2.extras.execute_values() <https://www.psycopg.org/docs/extras.html#psycopg2.extras.execute_values>`__ and common false positives (e.g. ``%`` in ``SECRET_KEY`` default value):
+-  Unnamed placeholders, except for log messages, ``strftime()``, `Cursor.executemany() <https://www.psycopg.org/psycopg3/docs/api/cursors.html#psycopg.Cursor.executemany>`__ and common false positives (e.g. ``%`` in ``SECRET_KEY`` default value):
 
    .. code-block:: none
 
-      (?<!info)(?<!debug|error)(?<!getenv)(?<!warning)(?<!critical|strftime)(?<!exception)(?<!execute_values)\((\n( *['"#].*)?)* *['"].*?%[^( ]
+      (?<!info)(?<!debug|error)(?<!getenv)(?<!warning)(?<!critical|strftime)(?<!exception)(?<!executemany)\((\n( *['"#].*)?)* *['"].*?%[^( ]
 
 -  Named placeholders, except for translation strings and :ref:`SQL statements<sql-statements>`:
 

docs/services/postgresql.rst

@@ -30,7 +30,7 @@ Identify the client
 Database administrators need to identify the sources of queries, in order to notify developers of inefficient queries or alert users whose queries will be interrupted by maintenance. For example:
 
 -  Django applications set the `application_name <https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-APPLICATION-NAME>`__ query string parameter in the PostgreSQL `connection URI <https://www.postgresql.org/docs/current/libpq-connect.html#id-1.7.3.8.3.6>`__, or use a service-specific user
--  Kingfisher Summarize uses the `psycopg2 <https://www.psycopg.org/docs/>`__ package, and adds ``/* kingfisher-summarize {identifier} */`` as a comment to expensive queries
+-  Kingfisher Summarize uses the `psycopg <https://www.psycopg.org/psycopg3/docs/>`__ package, and adds ``/* kingfisher-summarize {identifier} */`` as a comment to expensive queries
 -  Kingfisher Colab uses the `ipython-sql <https://pypi.org/project/ipython-sql/>`__ package, and adds the Google Colaboratory notebook URL as a comment to all queries
 
 Define tables

docs/services/rabbitmq.rst

@@ -85,7 +85,7 @@ Database commits
 
 If the consumer callback performs database operations, then all database operations before each message publication should be performed in a transaction. This ensures that, if the database operations fail and the incoming message is not acknowledged, then they have a chance to succeed when that message is redelivered, since no partial work had been committed. This guidance applies to *each* message publication, so that work is committed before the related message is published for further processing.
 
-The message publication should not be within the transaction block, if using a ``with`` statement with `psycopg2 <https://www.psycopg.org/docs/usage.html#with-statement>`__ or `Django <https://docs.djangoproject.com/en/5.2/topics/db/transactions/#django.db.transaction.atomic>`__. This ensures that the commit completes (e.g. without integrity errors), before a message is published for further processing.
+The message publication should not be within the transaction block, if using a ``with`` statement with `psycopg <https://www.psycopg.org/psycopg3/docs/basic/transactions.html#transaction-contexts>`__ or `Django <https://docs.djangoproject.com/en/5.2/topics/db/transactions/#django.db.transaction.atomic>`__. This ensures that the commit completes (e.g. without integrity errors), before a message is published for further processing.
 
 .. _rabbitmq-acknowledgment: