Skip to content

Releases: pgmq/pgmq

v1.7.0 - NOTIFY and Pop Many

11 Sep 00:30
e359dc9
Compare
Choose a tag to compare

New features 🚀

  • 🍿 pop many : -pop() now accepts an optional parameter qty which allows users to pop multiple messages at once - by @legion49f in #433
  • 🔔 notifications: server side functions which use NOTIFY to inform consumers when messages are available to be consumed. Usage requires client side implementation. Refer to these python tests for example usage. by @chrisprobst in #432

Changelog

New Contributors

Full Changelog: v1.6.1...v1.7.0

v1.6.1

18 Jul 22:06
0ad05d9
Compare
Choose a tag to compare

Bug fix

Full Changelog: v1.6.0...v1.6.1

v1.6.0

13 Jul 13:20
30b9fa9
Compare
Choose a tag to compare

Bug fixes

Other changes

New Contributors

Full Changelog: v1.5.1...v1.6.0

v1.5.1

21 Mar 20:44
7fd411d
Compare
Choose a tag to compare

What's Changed

  • Add note about conditional read being experimental by @v0idpwn in #370
  • Enable PGMQ to run without installing an extension by @axelfontaine in #379
  • Change pop() and set_vt() to use clock_timestamp() instead of now() by @brianpursley in #383

New Contributors

Full Changelog: v1.5.0...v1.5.1

v1.5.0

30 Dec 12:57
8e6df4b
Compare
Choose a tag to compare

Potentially breaking change

  • The delay parameter on pgmq.send() and pgmq.send_batch() now accepts either timestamptz or integer type, and will be a breaking change for any user using implicit type casting for the previous integer type, for both prepared statements and dynamic SQL. For example, pgmq.send('myq', '{"hello": "world"}', '10') would previously function correctly as Postgres could implicitly cast '10' string to an integer. The following are correct examples:
select pgmq.send('x', '{"hello": "world"}'); -- default value for `delay`
select pgmq.send('x', '{"hello": "world"}', 10); -- integer value
select pgmq.send('x', '{"hello": "world"}', '2024-12-01 02:29:20.889403+00'::timestamptz); -- explicit timestamptz

 

New Features

  • Experimental filter messages on pgmq.read() by using the conditional parameter. This feature is experimental and subject to change. #322
  • send and send_batch's delay parameter now accepts a timestamp in addition to integer #320
  • message headers now accepted on all messages #338

What's Changed

New Contributors

Full Changelog: v1.4.5...v1.5.0

v1.4.5

15 Nov 16:37
Compare
Choose a tag to compare

Bug fix:

Resolves a bug with pgmq.read_with_poll() that would result in high CPU utilization

Full Changelog: v1.4.4...v1.4.5

v1.4.4

17 Sep 10:44
9787166
Compare
Choose a tag to compare

What's Changed

  • Allow pg_partman to be installed in any schema by @olirice in #310

Full Changelog: v1.4.3...v1.4.4

v1.4.3

16 Sep 17:56
645a3c6
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.4.2...v1.4.3

v1.4.2

19 Aug 13:33
2783a6b
Compare
Choose a tag to compare

Breaking change:

The following characters are no longer allowed in queue names $, ', ;, --. It is recommended to create a new queue (without these characters), migrate client applications onto the new queue before running alter extension pgmq update to '1.4.2'.

What's Changed

Full Changelog: v1.4.1...v1.4.2

v1.4.1

15 Aug 13:54
78a766b
Compare
Choose a tag to compare

Security Patch - addresses SQL injection as described in #295

What's Changed

Full Changelog: v1.4.0...v1.4.1