Hi! I'm not using PgSQL in a cluster, but maybe gpSQL should provide some additional commands to help checking basic features, so that the RA does not need to know the internals.
Kind regards, Ulrich -----Original Message----- From: Users <users-boun...@clusterlabs.org> On Behalf Of Jehan-Guillaume de Rorthais via Users Sent: Monday, November 13, 2023 1:09 PM To: Windl, Ulrich <u.wi...@ukr.de> Cc: Jehan-Guillaume de Rorthais <j...@dalibo.com>; Cluster Labs - All topics related to open-source clustering welcomed <users@clusterlabs.org> Subject: [EXT] Re: [ClusterLabs] Re: PAF / pgSQL fails after OS/system shutdown - FIX On Mon, 13 Nov 2023 11:39:45 +0000 "Windl, Ulrich" <u.wi...@ukr.de> wrote: > But shouldn't the RA check for that (and act appropriately)? Interesting. I'm open to discuss this. Below my thoughts so far. Why the RA should check that? There's so many way to setup the system and PostgreSQL, where should the RA stop checking for all possible way to break it? The RA checks various (maybe too many) things related to the instance itself already. I know various other PostgreSQL setups that would trigger errors in the cluster if the dba doesn't check everything is correct. I'm really reluctant to add add a fair amount of code in the RA to correctly parse and check the complex PostgreSQL's setup. This would add complexity and bugs. Or maybe I could add a specific OCF_CHECK_LEVEL sysadmins can trigger by hand before starting the cluster. But I wonder if it worth the pain, how many people will know about this and actually run it? The problem here is that few users actually realize how the postgresql-common wrapper works and what it actually does behind your back. I really appreciate this wrapper, I do. But when you setup a Pacemaker cluster, you either have to bend to it when setting up PAF (as documented), or avoid it completely. PAF is all about drawing a clear line between the sysadmin job and the dba one. Dba must build a cluster of instances ready to start/replicate with standard binaries (not wrappers) before sysadmin can set up the resource in your cluster. Thoughts? > -----Original Message----- > From: Users <users-boun...@clusterlabs.org> On Behalf Of Jehan-Guillaume de > Rorthais via Users Sent: Friday, November 10, 2023 1:13 PM > To: lejeczek via Users <users@clusterlabs.org> > Cc: Jehan-Guillaume de Rorthais <j...@dalibo.com> > Subject: [EXT] Re: [ClusterLabs] PAF / pgSQL fails after OS/system shutdown - > FIX > > On Fri, 10 Nov 2023 12:27:24 +0100 > lejeczek via Users <users@clusterlabs.org> wrote: > ... > > > > > to share my "fix" for it - perhaps it was introduced by > > OS/packages (Ubuntu 22) updates - ? - as oppose to resource > > agent itself. > > > > As the logs point out - pg_stat_tmp - is missing and from > > what I see it's only the master, within a cluster, doing > > those stats. > > That appeared, I use the word for I did not put it into > > configs, on all nodes. > > fix = to not use _pg_stat_tmp_ directive/option at all. > > Of course you can use "pg_stat_tmp", just make sure the temp folder exists: > > cat <<EOF > /etc/tmpfiles.d/postgresql-part.conf > # Directory for PostgreSQL temp stat files > d /var/run/postgresql/14-paf.pg_stat_tmp 0700 postgres postgres - - > EOF > > To take this file in consideration immediately without rebooting the server, > run the following command: > > systemd-tmpfiles --create /etc/tmpfiles.d/postgresql-part.conf > _______________________________________________ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users > > ClusterLabs home: https://www.clusterlabs.org/ > _______________________________________________ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users > > ClusterLabs home: https://www.clusterlabs.org/ _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/ _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
