Psycopg2-mq

Latest version: v0.13.5

Safety actively analyzes 723177 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 8 of 10

0.4.1

------------------

- Attempt to reconnect to the database after losing the connection.
If the reconnect attempt fails then crash.

0.4

----------------

- [model migration] Add a ``worker`` column to the ``Job`` model to track what
worker is handling a job.

- Add an optional ``name`` argument to ``MQWorker`` to name the worker -
the value will be recorded in each job.

- Add a ``threads`` argument (default=``1``) to ``MQWorker`` to support
handling multiple jobs from the same worker instance instead of making a
worker per thread.

- Add ``capture_signals`` argument (default=``True``) to ``MQWorker`` which
will capture ``SIGTERM``, ``SIGINT`` and ``SIGUSR1``. The first two will
trigger graceful shutdown - they will make the process stop handling new
jobs while finishing active jobs. The latter will dump to ``stderr`` a
JSON dump of the current status of the worker.

0.3.3

------------------

- Only save a cursor update if the job is completed successfully.

0.3.2

------------------

- Mark lost jobs during timeouts instead of just when a worker starts in order
to catch them earlier.

0.3.1

------------------

- When attempting to schedule a job with a cursor and a ``scheduled_time``
earlier than a pending job on the same cursor, the job will be updated to
run at the earlier time.

- When attempting to schedule a job with a cursor and a pending job already
exists on the same cursor, a ``conflict_resolver`` function may be
supplied to ``MQSource.call`` to update the job properties, merging the
arguments however the user wishes.

0.3

----------------

- [model migration] Add a new column ``cursor_snapshot`` to the ``Job`` model which
will contain the value of the cursor when the job begins.

Page 8 of 10

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.