tgindex
PostgreSQL DBA

PostgreSQL DBA

Статистика
@postgres_techанглийский

Sharing knowledge about postgresql database

Последний пост
10 авг.
Последнее чтение
14 авг.
Постов за неделю
0
Всего постов
20
Тип
открытый
Язык
английский
В каталоге с
13 авг.
Подписчики
2 023
+2 за 3 дн.
Сутки
+1
+0,05%
Неделя
 
Месяц
 
Просмотров на пост
379
20 постов
Вовлечённость
18,7%
к подписчикам
Постов в день
0,0
всего 20
Упоминаний
0
каналов
Охват размещения
оценка
1/24сутки в ленте
143
1/48двое суток
163
1/72трое суток
176

Оценка по просмотрам недавних постов: пост набирает почти всё за первые сутки.

Посты

  • https://patroni.readthedocs.io/en/latest/README.html

  • Patroni is a widely used solution for managing PostgreSQL high availability. It provides a robust framework for automatic failover, cluster management, and operational simplicity in PostgreSQL environments.  https://www.cybertec-postgresql.com/en/patroni-cascading-replication-with-stanby-cluster/

  • Cascading Replication https://www.cybertec-postgresql.com/en/patroni-cascading-replication-with-stanby-cluster/

  • https://stormatics.tech/blogs/the-1-gb-limit-that-breaks-pg_prewarm-at-scale

  • Schemas in PostgreSQL and Oracle: what is the difference? https://www.cybertec-postgresql.com/en/schema-postgresql-oracle-difference/

  • без подписи

  • без подписи

  • без подписи

  • без подписи

  • Configuration Parameters

  • CREATE TABLE orders ( order_id SERIAL PRIMARY KEY, customer_id INTEGER, order_date DATE, order_total NUMERIC ) PARTITION BY RANGE (order_date); CREATE TABLE orders_y2023 PARTITION OF orders FOR VALUES FROM ('2023-01-01') TO ('2024-01-01'); CREATE TABLE orders_y2024 PARTITION OF orders FOR VALUES FROM ('2024-01-01') TO ('2025-01-01'); -- Add an index to each partition CREATE INDEX idx_orders_y2023_customer_id ON orders_y2023 (customer_id); CREATE INDEX idx_orders_y2024_customer_id ON orders_y2024 (customer_id);

  • без подписи

  • без подписи

  • без подписи

  • Beyond indexing, several query optimization techniques can significantly improve performance.

  • Unused Indexes: Identify and remove unused indexes to reduce write overhead. The pg_stat_all_indexes view provides information about index usage.

  • Index Bloat: As data is inserted, updated, and deleted, indexes can become fragmented and bloated, leading to performance degradation. Rebuild indexes periodically using the REINDEX command.

  • Statistics: PostgreSQL relies on statistics to estimate the cost of different query plans. Inaccurate statistics can lead to suboptimal plan choices. Regularly update statistics using the ANALYZE command.

  • Partial indexes index only a subset of the table's rows, based on a condition. This can reduce index size and improve performance when queries frequently filter on that condition.

  • Composite indexes index multiple columns. The order of columns in a composite index is important. The most frequently used column in WHERE clauses should come first.