Lastest docker image is running older version of pgmq

[craigpastro]

👋 I think this is not expected, but please let me know.

I've pulled the lasted Docker image and it is still using v0.11.0 of the pgmq extension.

postgres=# \dx
                                     List of installed extensions
  Name   | Version |   Schema   |                             Description
---------+---------+------------+---------------------------------------------------------------------
 pgmq    | 0.11.0  | public     | A lightweight message queue. Like AWS SQS and RSMQ but on Postgres.
 plpgsql | 1.0     | pg_catalog | PL/pgSQL procedural language
(2 rows)

I would have expected v0.11.2. In particular, when I try to drop a queue I get:

postgres=# select pgmq_drop_queue('foo');
ERROR:  relation "public.part_config" does not exist
LINE 1: DELETE FROM public.part_config where parent_table = 'public....
                    ^
QUERY:  DELETE FROM public.part_config where parent_table = 'public.pgmq_foo';

Thanks!

Edit: just to confirm which image I am running:

$ docker images --digests
REPOSITORY                                                TAG                                                                          DIGEST                                                                    IMAGE ID       CREATED          SIZE
quay.io/tembo/pgmq-pg                                     latest                                                                       sha256:3392ae1f425dadb5c2204c3fdb3409467b374de169c27c989cfc62bd07120931   384b8a6f4e08   48 minutes ago   1.32GB

[ChuckHend]

There was a bug in 0.11.0 that was fixed in 0.11.1. Unfortunately our CI is not triggering new image builds on every release...yet. An image with 0.11.2 is being built right now though.

[ChuckHend]

Looks like its done now. I'm going to close this an open another issue to move the image builds into the extension publish pipeline. Thanks for pointing this out!

[ChuckHend]

Thanks @craigpastro https://github.com/tembo-io/pgmq/issues/42

[craigpastro]

Thanks for the update @ChuckHend!