0

I'm trying to benchmark postgresql in hammerdb getting below error:

Vuser 1:Checkpoint and Vacuum
Error in Virtual User 1: ERROR:  must be superuser to do CHECKPOINT
Vuser 1:FINISHED FAILED
Vuser 13:FINISHED SUCCESS
Vuser 18:FINISHED SUCCESS
Vuser 8:FINISHED SUCCESS
Vuser 5:FINISHED SUCCESS
Vuser 21:FINISHED SUCCESS
Vuser 9:FINISHED SUCCESS
Vuser 16:FINISHED SUCCESS
Vuser 20:FINISHED SUCCESS
Vuser 6:FINISHED SUCCESS
Vuser 14:FINISHED SUCCESS
Vuser 19:FINISHED SUCCESS
Vuser 11:FINISHED SUCCESS
Vuser 15:FINISHED SUCCESS
Vuser 17:FINISHED SUCCESS
Vuser 7:FINISHED SUCCESS
Vuser 3:FINISHED SUCCESS
Vuser 10:FINISHED SUCCESS
Vuser 12:FINISHED SUCCESS
Vuser 2:FINISHED SUCCESS
Vuser 4:FINISHED SUCCESS
ALL VIRTUAL USERS COMPLETE
runtimer returned after 416 seconds
vudestroy success
TEST SEQUENCE COMPLETE

Any suggestion to fix this issue and which user to be mapped as super user.

  • Use a database user that has superuser permissions – Frank Heikens Mar 03 '22 at 13:03
  • how can I check which user has superuser permission or do I need to give postgres user with sudo permission –  Mar 04 '22 at 04:50
  • 1
    Check the results from SELECT * FROM pg_roles; The user "postgres" is usually superuser. – Frank Heikens Mar 04 '22 at 08:58
  • I'm able to fetch the details but unable to confirm if the user has superuser privilege's or not: Below is the output, can you please help to enable superuser permission: –  Mar 04 '22 at 10:47
  • rolname | rolsuper | rolinherit | rolcreaterole | rolcreatedb | rolcanlogin | rolreplication | rolconnlimit | rolpassword | rolvaliduntil | rolbypassrl s | rolconfig | oid ---------------------------+----------+------------+---------------+-------------+-------------+----------------+--------------+-------------+--------------- postgres | f | t | t | t | t | f | -1 | ******** | | f | | 16389 –  Mar 04 '22 at 10:47
  • 1
    Second column, "rolsuper" says "t" from true. – Frank Heikens Mar 04 '22 at 11:24

1 Answers1

0

You can disable HammerDB from calling checkpoint and vacuum at the end of a test with the following command:

hammerdb>diset tpcc pg_vacuum false
Changed tpcc:pg_vacuum from true to false for PostgreSQL

If running long running or multiple tests on PostgreSQL it is recommended to enable Autovacuum to ensure that vacuuming is ongoing during tests to prevent bloat. When autovacuum is enabled it is not necessary to do so manually.

user131743
  • 51
  • 1