¡Ya disponible! Investigación de Telegram 2025 — los principales insights del año 
PostgreSQL DBA
Ir al canal en Telegram
2 024
Suscriptores
-124 horas
+17 días
-730 días
Carga de datos en curso...
Canales Similares
Nube de Etiquetas
Menciones Entrantes y Salientes
---
---
---
---
---
---
Atraer Suscriptores
junio '26
junio '26
+4
en 0 canales
mayo '26
+14
en 0 canales
Get PRO
abril '26
+17
en 0 canales
Get PRO
marzo '26
+14
en 0 canales
Get PRO
febrero '26
+15
en 0 canales
Get PRO
enero '26
+23
en 0 canales
Get PRO
diciembre '25
+17
en 0 canales
Get PRO
noviembre '25
+37
en 0 canales
Get PRO
octubre '25
+34
en 0 canales
Get PRO
septiembre '25
+27
en 0 canales
Get PRO
agosto '25
+38
en 0 canales
Get PRO
julio '25
+31
en 0 canales
Get PRO
junio '25
+26
en 0 canales
Get PRO
mayo '25
+34
en 0 canales
Get PRO
abril '25
+34
en 0 canales
Get PRO
marzo '25
+42
en 0 canales
Get PRO
febrero '25
+40
en 0 canales
Get PRO
enero '25
+46
en 0 canales
Get PRO
diciembre '24
+60
en 0 canales
Get PRO
noviembre '24
+74
en 0 canales
Get PRO
octubre '24
+60
en 0 canales
Get PRO
septiembre '24
+82
en 0 canales
Get PRO
agosto '24
+1 752
en 0 canales
| Fecha | Crecimiento de Suscriptores | Menciones | Canales | |
| 06 junio | 0 | |||
| 05 junio | 0 | |||
| 04 junio | 0 | |||
| 03 junio | +1 | |||
| 02 junio | +1 | |||
| 01 junio | +2 |
Publicaciones del Canal
| 2 |  Sin texto... | 275 |
| 3 |  Sin texto... | 265 |
| 4 |  Configuration Parameters | 253 |
| 5 | 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); | 204 |
| 6 |  Sin texto... | 161 |
| 7 |  Sin texto... | 167 |
| 8 |  Sin texto... | 147 |
| 9 |  Beyond indexing, several query optimization techniques can significantly improve performance. | 129 |
| 10 | Unused Indexes: Identify and remove unused indexes to reduce write overhead. The pg_stat_all_indexes view provides information about index usage. | 131 |
| 11 | 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. | 127 |
| 12 | 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. | 132 |
| 13 | 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. | 137 |
| 14 | 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. | 135 |
| 15 |  Sin texto... | 132 |
| 16 | Indexes are crucial for improving query performance, but they also add overhead to write operations. Choosing the right indexes and maintaining them properly is essential. | 138 |
| 17 | Filtering: Where clauses that filter the data. If a filter is being applied after a large amount of data has already been processed, this is a sign the query could be optimized. | 134 |
| 18 | Rows: The estimated number of rows returned by each operation. Significant discrepancies between estimated and actual rows (observed with EXPLAIN ANALYZE) can indicate inaccurate statistics, leading the planner to choose a suboptimal plan. | 126 |
| 19 | Cost: The estimated cost of each operation. The planner uses a cost model to estimate the resources required to perform each operation. Higher costs usually indicate potential bottlenecks. | 121 |
| 20 |  Sin texto... | 122 |
