Postgres: Manually analyze

 ANALYZE table_name;

-- Analyzes the "table_name" table ANALYZE schema_name.table_name; -- Analyzes the "table_name" table within the "schema_name" schema ANALYZE database_name; -- Analyzes all tables within the "database_name" database

Comments

Post a Comment

Popular posts from this blog

Postgres: To list table owners

SELECT schemaname, tablename, tableowner FROM pg_tables WHERE schemaname NOT IN ('pg_catalog', 'information_schema') ORDER BY tableowner, schemaname, tablename; ---- SELECT schemaname, tablename, tableowner FROM pg_tables WHERE schemaname <> tableowner AND  schemaname NOT IN ('pg_catalog', 'information_schema') ORDER BY tableowner, schemaname, tablename;
Read more

PeopleSoft: Clean Up PUM

  Manual Cleanup steps for WINDOWS Before carrying out the advanced steps in this section: Run the command:  psft-dpk-setup.bat --cleanup. If you deployed the environment using the use_alternate_puppet_install option, use this command:   psft-dpk-setup.bat --cleanup --use_alternate_puppet_install If the script displays a FAILED message, run it again. If it succeeds, check the BASE_DIR folders to be sure everything has been deleted. If the BASE_DIR folders are not clear, or if a subsequent deployment is not successful, carry out the steps below. For the  ADVANCED CLEAN UP PROCESS  on Microsoft Windows, please see the following steps. NOTE: These should be performed by someone familiar with modifying the Microsoft Windows registry. Depending upon where the cleanup process failed, some of the items mentioned in these steps may have already been removed. The user should remove whatever remains in this order: Start the Microsoft Windows Services utilit...
Read more

Postgres: Clean up stopped replication slot

Image
  When a slot is inactive, that means that Murty and his team have stopped the replication on their side. The SQL below will identify inactive slots. We should schedule this script in a job , running every hour.    (1) SELECT  slot_name,  pg_size_pretty(pg_wal_lsn_diff(pg_current_wal_lsn(),restart_lsn)) AS size,  active,  slot_type  FROM pg_replication_slots;       (2) Once you identify the replication slot, the job should drop it with the following command:     SELECT pg_drop_replication_slot ('pg_replication_slot_name_from_above');         (3) Restart the database instance to clean up unwanted disk space.   Notes from Google:- Thank you for contacting Google Cloud Support. My name is Jagadeesh and I will be assisting you with this issue.   I understand that WAL logs are expanding to over 1.5TB and you want to know what is causing WAL logs to grow and you want to reduce it. Please confirm if ...
Read more