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

• docs: Community PGMQ TypeScript Client Support for Deno by @tmountain in #311
• docs: Community PGMQ TypeScript Client Support for NodeJs and Midway.js, supports transaction by @waitingsong in #312
• pgmq-python: adding support for Transaction by @tavallaie in #268
• release tembo-pgmq-python v0.9.0 by @ChuckHend in #314
• add pg17 support by @ChuckHend in #313
• added truncate instead of delete by @Abiji-2020 in #321
• update pgmq.control reference by @emmanuel-ferdman in #327
• add migration sql for purge queue upgrade by @ChuckHend in #325
• Make drop queue infer queue type by @Neptune650 in #319
• Add new conditional parameter for read by @Neptune650 in #322
• add test for reading null message by @ChuckHend in #329
• Fix gitignore for SQL extension files by @fabriziomello in #331
• Add queue_visible_length to pgmq.metrics by @v0idpwn in #332
• Add timestamp support in send and send_batch by @Neptune650 in #320
• Makefile: use pg_config path from environment variable instead of hardcoded binary by @palash25 in #336
• Fix error when PG_CONFIG not explicitly defined, plus support development pg versions by @v0idpwn in #337
• Add Installation Guide for PGMQ by @Saturn225 in #323
• Add devcontainer for Python environment by @jason810496 in #339
• Update the pgmq extension README to utilize the Scarf Gateway by @arjundevarajan in #330
• style: simplify statements for readability by @hamirmahal in #341
• Fix regression: not respecting interval in read_with_poll by @v0idpwn in #343
• [chore] don't publish from forks by @rotty3000 in #346
• bitnami compatible image by @rotty3000 in #348
• Add Supabase to "Who uses pgmq?" by @jumski in #351
• Implement message headers by @v0idpwn in #338
• Rename pgmq--1.4.4--1.5.0.sql to pgmq--1.4.5--1.5.0.sql by @za-arthur in #355
• drop pg12 support and publish pg17 to pgt.dev by @ChuckHend in #356
• docs to clarify read_with_poll param qty by @elvizlai in #358
• fix: python logging by @elvizlai in #360
• Add created sequence object to the extension by @za-arthur in #352
• prep v1.5.0 by @ChuckHend in #361

New Contributors

• @tmountain made their first contribution in #311
• @waitingsong made their first contribution in #312
• @Abiji-2020 made their first contribution in #321
• @emmanuel-ferdman made their first contribution in #327
• @Neptune650 made their first contribution in #319
• @fabriziomello made their first contribution in #331
• @palash25 made their first contribution in #336
• @Saturn225 made their first contribution in #323
• @arjundevarajan made their first contribution in #330
• @rotty3000 made their first contribution in #346
• @jumski made their first contribution in #351
• @za-arthur made their first contribution in #355
• @elvizlai made their first contribution in #358

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