Chris Travers wrote:
> If one releases an extension with say a version number of 0.1 and then
releases one with important
> changes at 0.2, how is the best way to manage these changes? I
couldn't find anything in the docs to
> discuss this issue. Am I missing something?
>
> Specifically for pg_m
If one releases an extension with say a version number of 0.1 and then
releases one with important changes at 0.2, how is the best way to manage
these changes? I couldn't find anything in the docs to discuss this issue.
Am I missing something?
Specifically for pg_message_queue, for 0.2 I would l
