Project

General

Profile

Actions

Bug #22128

open

Wrong Table name inside documentation

Added by Alexis TARUSSIO 16 days ago. Updated 15 days ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Documentation
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
I hate Rudder for that
User visibility:
First impressions of Rudder
Effort required:
Priority:
128
Regression:
No

Description

Hello,

As I explain on gitter, we follow the maintenance's documentation for 7.2 : https://docs.rudder.io/reference/7.2/administration/procedures.html

It says:

Manual vacuuming using the psql binary
# You can either use sudo to change owner to the postgres user, or use the rudder connection credentials.

# With sudo:
sudo -u postgres psql -d rudder

# With rudder credentials, it will ask the password in this case:
psql -u rudder -d rudder

# And then, when you are connected to the rudder database in the psql shell, trigger a vacuum:
rudder# VACUUM FULL rudder;
rudder# VACUUM FULL archivedruddersysevents;
rudder# VACUUM FULL nodecompliancelevels;

We don't have any table named rudder:

udder=# \dt
                    Liste des relations
 Schéma |            Nom             | Type  | Propriétaire 
--------+----------------------------+-------+--------------
 public | archivednodecompliance     | table | rudder
 public | archivednodeconfigurations | table | rudder
 public | archivedruddersysevents    | table | rudder
 public | campaignevents             | table | rudder
 public | changerequest              | table | rudder
 public | eventlog                   | table | rudder
 public | gitcommit                  | table | rudder
 public | migrationeventlog          | table | rudder
 public | nodecompliance             | table | rudder
 public | nodecompliancelevels       | table | rudder
 public | nodeconfigurations         | table | rudder
 public | nodes_info                 | table | rudder
 public | reportsexecution           | table | rudder
 public | rudderproperties           | table | rudder
 public | ruddersysevents            | table | rudder
 public | statusupdate               | table | rudder
 public | workflow                   | table | rudder
(17 lignes)

But when we look for the bigest table, we got : ruddersysevents

rudder=# select relname, pg_size_pretty(pg_total_relation_size(relname::regclass)) as full_size, pg_size_pretty(pg_relation_size(relname::regclass)) as table_size, pg_size_pretty(pg_total_relation_size(relname::regclass) - pg_relation_size(relname::regclass)) as index_size from pg_stat_user_tables order by pg_total_relation_size(relname::regclass) desc limit 10;
       relname        | full_size | table_size | index_size 
----------------------+-----------+------------+------------
 ruddersysevents      | 12 GB     | 9525 MB    | 2734 MB
 nodecompliancelevels | 1873 MB   | 1000 MB    | 873 MB
 reportsexecution     | 120 MB    | 51 MB      | 69 MB
 eventlog             | 53 MB     | 32 MB      | 21 MB
 nodeconfigurations   | 19 MB     | 864 kB     | 18 MB
 gitcommit            | 952 kB    | 496 kB     | 456 kB
 nodes_info           | 640 kB    | 544 kB     | 96 kB
 rudderproperties     | 64 kB     | 8192 bytes | 56 kB
 statusupdate         | 64 kB     | 8192 bytes | 56 kB
 nodecompliance       | 40 kB     | 0 bytes    | 40 kB

Alexis said it's the right one.

Can you update the documentation ?

best regards,

Alexis TARUSSIO

Actions #1

Updated by Vincent MEMBRÉ 15 days ago

  • Target version changed from 7.2.2 to 7.2.3
Actions

Also available in: Atom PDF