We use MySQL for all our our development and testing. I do not believe the pgsql plugin ever was fully functional and has been largely untouched for a couple of years. You are welcome to work on it if you want and send patches to the list with the work.
Quoting Hongjia Cao <[email protected]>: > > I don't think it is maintained. I tried to keep it working as > accounting_storage/mysql but I gave up. The logic about the association > will not work, and I'm not sure about the job accounting function. > Without the association logic, some other features such as > priority/multifactor will not work. > > 在 2013-01-13日的 07:36 -0700，Yair Yarom写道： >> >> Hi list, >> >> I'm new to slurm, so apologies if this is not the place for these >> questions, or if they were answered elsewhere that I haven't found. >> >> What is the current status of the accounting_storage/pgsql plugin? Is it >> operational/maintained? >> >> It is simpler for us to maintain a postgresql database rather then a >> mysql database. And I'm not sure we need the associations which, I >> admit, I haven't fully grasped what they do. So can someone give me some >> examples of specific features that will be missing if I use the >> postgresql backend? >> >> Is it documented how to set up the database? >> Besides the 3 lines in accounting_storage_pgsql.c (create user, create >> db, create plpgsql), I've noticed there's a bug while creating the >> initial database (patch included against the slurm-2.5 branch). And I >> needed to add the cluster using sacctmgr (to avoid the 'cluster not in >> db' messages). >> >> However now I'm getting 'cluster not registered' messages, which I'm not >> sure what they mean, or if they're important, as basic sacct seems to >> work. >> >> After restarting, the slurmdbd is having troubles to start, with >> e.g. (It sometimes segfaults on other queries): >> slurmdbd: debug3: >> as/pg(../../../../../slurm.git/src/plugins/accounting_storage/pgsql/as_pg_rollup.c:1015) >> >> query >> SELECT hourly_rollup, daily_rollup, monthly_rollup FROM >> testc.last_ran_table LIMIT 1 >> column number 3 is out of range 0..2 >> slurmdbd: error: PQexec failed: 7 >> slurmdbd: query was SELECT hourly_rollup, daily_rollup, >> monthly_rollup FROM testc.last_ran_table LIMIT 1 >> Segmentation fault >> >> However after a couple of tries, it succeeds in running. But the >> 'cluster not registered' messages are still there. >> >> If I do work with one backend, is there any utility to convert the >> already gathered data from one backend to another? >> >> Thanks in advance, >> Yair. >> >> >> >> diff --git a/src/plugins/accounting_storage/pgsql/as_pg_qos.c >> b/src/plugins/accounting_storage/pgsql/as_pg_qos.c >> index a78d527..880efce 100644 >> --- a/src/plugins/accounting_storage/pgsql/as_pg_qos.c >> +++ b/src/plugins/accounting_storage/pgsql/as_pg_qos.c >> @@ -459,7 +459,7 @@ check_qos_tables(PGconn *db_conn) >> "(%ld, %ld, 0, 0, $$%s$$, $$%s$$, " >> "NULL, NULL, NULL, NULL, NULL, NULL, NULL, " >> "NULL, NULL, NULL, NULL, NULL, NULL, NULL, " >> - "'', 0, 0, 1.0)" >> + "NULL, '', 0, 0, 1.0)" >> ")", >> (long)now, (long)now, >> /* deleted=0, id not used */ qos, desc > >
