Hologres:Billing

The fees are calculated by using the following formula:

Fees for a query job = Amount of input data × Unit price

The following table provides the pricing information.

Hologres Shared Cluster (Lakehouse Acceleration Edition) uses the pay-as-you-go billing method based on the amount of data scanned by using SQL statements. The lifecycle management of a pay-as-you-go Hologres Shared Cluster (Lakehouse Acceleration Edition) instance complies with the following rules:

• After you purchase a Hologres Shared Cluster (Lakehouse Acceleration Edition) instance on the international site (alibabacloud.com), you can use the instance. The system summarizes the total amount of data scanned by all SQL statements in the previous day and sends you bills. The system automatically deducts the amount payable from the balance of your Alibaba Cloud account.

• If your Alibaba Cloud account has overdue payments, all instances that belong to your Alibaba Cloud account become overdue. The instances run normally if the overdue payment is less than USD 1,000.

• If the overdue payment in your account reaches USD 1,000 and the deduction fails, the instances run normally within 14 days.

• On the fifteenth day after the deduction fails, the instances stop providing services and are locked. You cannot access the instances. During this period, the system does not send you bills.

• On the fifteenth day after the instances stop providing services due to an overdue payment, the instances are released and deleted from the console. Data in the instances is also deleted and cannot be restored.

You can view the query details of all users as a superuser. RAM users can view information about SQL statements that they run. Sample statement:

select usename,status,query_id,command_tag,duration,query,read_bytes,application_name FROM hologres.hg_query_log;

For more information about SQL queries, see Manage queries.

You must have specific permissions to query the amount of scanned data. This section describes the permission rules and authorization methods.

• Query the amount of data scanned for all databases in an instance.

  • Grant the superuser permissions to a user.

    A superuser can view the amount of data scanned for all databases in an instance. Execute the following statement to assign the superuser role to a user:

    -- Replace Account ID with the Alibaba Cloud account ID of the user. If the user is a RAM user, prefix the account ID with p4_. 
    ALTER USER "Account ID" SUPERUSER;

  • Add another user to the pg_read_all_stats user group.

    In addition to superusers, users in the pg_read_all_stats user group have permissions to query the amount of data scanned for all databases in the relevant Hologres instance. If you are a superuser, you can add regular users to this user group. To add a user to this user group, execute one of the following statements:

    GRANT pg_read_all_stats TO "Account ID"; -- Use the standard PostgreSQL authorization model to grant related permissions to the user.
    CALL spm_grant('pg_read_all_stats', 'Account ID'); -- Use the simple permission model (SPM) to grant related permissions to the user.
    CALL slpm_grant('pg_read_all_stats', 'Account ID'); -- Use the schema-level permission model (SLPM) to grant related permissions to the user.

• View the amount of data scanned for the specified database.

  Users in the db_admin user group have permissions to query the amount of data scanned for the specified database in the relevant Hologres instance. If you are a superuser, you can add regular users to this user group by using the SPM or SLPM.

  CALL spm_grant('<db_name>_admin', 'Account ID'); -- Use the SPM to grant related permissions to the user.
  CALL slpm_grant('<db_name>.admin', 'Account ID'); -- Use the SLPM to grant related permissions to the user.

• Regular users have permissions to query the amount of data scanned by themselves for the database within the relevant Alibaba Cloud account.

For more information about the management of permissions, see Permission management overview.

You can execute the following SQL statement to check detailed data. Make sure that the user who executes the SQL statement is assigned the superuser role of the Hologres Shared Cluster (BI-based MaxCompute Acceleration Edition) instance.

show log_min_duration_statement;

• Syntax

  select  to_char(query_end,'DD Mon YYYY') as day
          ,round(
              sum(
                  case when read_bytes < 10*1024*1024 then 10*1024*1024
                  else read_bytes end
              )/1024/1024
          ) as "scan_size_mb" -- Scan at least 10 MB of data per query job.
          ,count(*) as "sql_count"
  from    hologres.hg_query_log
  where   status = 'SUCCESS'
  and     command_tag in ('SELECT')
  and     read_bytes is not null
  and     query_end >= 'Start time'::TIMESTAMPTZ
  and     query_end < 'End time'::TIMESTAMPTZ
  group by 1
  order by 3 desc;

• Example

  Execute the following SQL statement to query the amount of scanned data from 10:00 on January 1, 2022 to 11:00 on January 1, 2022:

  select to_char(query_end,'DD Mon YYYY') as day
          ,round(
              sum(
                  case when read_bytes < 10*1024*1024 then 10*1024*1024
                  else read_bytes end
              )/1024/1024
          ) as "scan_size_mb" -- Scan at least 10 MB of data per query job.
          ,count(*) as "sql_count"
  from    hologres.hg_query_log
  where   status = 'SUCCESS'
  and     command_tag in ('SELECT')
  and     read_bytes is not null
  and     query_end >= '2022-01-01 10:00:00+08'::TIMESTAMPTZ
  and     query_end < '2022-01-01 11:00:00+08'::TIMESTAMPTZ
  group by 1
  order by 3 desc;

You can execute the following SQL statement to query the amount of data scanned by using each SQL statement over a period of time. Make sure that the user who executes the SQL statement is assigned the superuser role of the Hologres Shared Cluster (BI-based MaxCompute Acceleration Edition) instance.

• Syntax

  select  usename
          ,status
          ,query_id
          ,datname
          ,command_tag
          ,duration
          ,message
          ,query_start
          ,query_end
          ,query_date
          ,query
          ,case when read_bytes < 10*1024*1024 then 10*1024*1024
           else read_bytes end as billing_read_bytes -- Scan at least 10 MB of data by using each SQL statment.
          ,application_name
  from    hologres.hg_query_log
  where   status = 'SUCCESS'
  and     command_tag in ('SELECT')
  and     read_bytes is not null
  and     query_end >= 'Start time'::TIMESTAMPTZ
  and     query_end < 'End time'::TIMESTAMPTZ
                                  

  The billing_read_bytes field indicates the amount of scanned data used for billing.

• Example

  Execute the following SQL statement to query the amount of data scanned by using each SQL statement from 10:00 on March 1, 2022 to 11:00 on March 1, 2022:

  select  usename
          ,status
          ,query_id
          ,datname
          ,command_tag
          ,duration
          ,message
          ,query_start
          ,query_end
          ,query_date
          ,query
          ,case when read_bytes < 10*1024*1024 then 10*1024*1024
           else read_bytes end as billing_read_bytes -- Scan at least 10 MB of data by using each SQL statment.
          ,application_name
  from    hologres.hg_query_log
  where   status = 'SUCCESS'
  and     command_tag in ('SELECT')
  and     read_bytes is not null
  and     query_end >= '2022-03-01 10:00:00+08'::TIMESTAMPTZ
  and     query_end < '2022-03-01 11:00:00+08'::TIMESTAMPTZ;