From: Dominik Csapak <d.csapak@proxmox.com>
To: Stoiko Ivanov <s.ivanov@proxmox.com>, pmg-devel@lists.proxmox.com
Subject: [pmg-devel] applied: [PATCH pmg-api 0/2] cluster changes for bookworm
Date: Tue, 27 Jun 2023 10:29:04 +0200 [thread overview]
Message-ID: <4c5a68a5-9c12-455b-57b0-1a779d5ff6c0@proxmox.com> (raw)
In-Reply-To: <20230626204510.34783-1-s.ivanov@proxmox.com>
applied series, with the fixup squashed in like we talked off-list
thanks
On 6/26/23 22:45, Stoiko Ivanov wrote:
> with the initial tests for the upgrade of the pmg packages to bookworm I
> noticed 2 small issues when running PMG in a cluster.
>
> the first patch addresses the same issue we had in pve-cluster with the
> deprecated rsync syntax.
>
> the second patch addresses a change in postgresql's response to
> ```
> EXTRACT(EPOCH FROM now())
> ```
>
> with both patches applied a cluster setup with one being upgraded from
> bullseye (with a restored backup from another bullseye system) and one
> installed directly from a test ISO remain with both nodes in active state.
>
> Stoiko Ivanov (2):
> cluster: fix rsync invocation
> postgresql compat: cast result from EXTRACT to INTEGER
>
> src/PMG/Cluster.pm | 4 +++-
> src/PMG/DBTools.pm | 4 ++--
> src/PMG/Quarantine.pm | 4 ++--
> src/PMG/Statistic.pm | 16 ++++++++--------
> src/bin/pmgpolicy | 2 +-
> 5 files changed, 16 insertions(+), 14 deletions(-)
>
prev parent reply other threads:[~2023-06-27 8:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 20:45 [pmg-devel] " Stoiko Ivanov
2023-06-26 20:45 ` [pmg-devel] [PATCH pmg-api 1/2] cluster: fix rsync invocation Stoiko Ivanov
2023-06-26 20:45 ` [pmg-devel] [PATCH pmg-api 2/2] postgresql compat: cast result from EXTRACT to INTEGER Stoiko Ivanov
2023-06-27 8:29 ` Dominik Csapak [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4c5a68a5-9c12-455b-57b0-1a779d5ff6c0@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=pmg-devel@lists.proxmox.com \
--cc=s.ivanov@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.