Skip to content

v1.5.0

Latest
Compare
Choose a tag to compare
@ChuckHend ChuckHend released this 30 Dec 12:57
· 3 commits to main since this release
8e6df4b

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