8 490
Subscribers
+124 hours
-17 days
-2730 days
Data loading in progress...
Similar Channels
Tags Cloud
No data
Any problems? Please refresh the page or contact our support manager.
Incoming and Outgoing Mentions
---
---
---
---
---
---
Attracting Subscribers
July '26
July '26
+50
in 0 channels
June '26
+41
in 0 channels
Get PRO
May '26
+49
in 0 channels
Get PRO
April '26
+44
in 0 channels
Get PRO
March '26
+41
in 0 channels
Get PRO
February '26
+59
in 0 channels
Get PRO
January '26
+64
in 0 channels
Get PRO
December '25
+69
in 0 channels
Get PRO
November '25
+64
in 0 channels
Get PRO
October '25
+81
in 0 channels
Get PRO
September '25
+83
in 0 channels
Get PRO
August '25
+101
in 0 channels
Get PRO
July '25
+121
in 0 channels
Get PRO
June '25
+73
in 0 channels
Get PRO
May '25
+113
in 0 channels
Get PRO
April '25
+108
in 0 channels
Get PRO
March '25
+127
in 0 channels
Get PRO
February '25
+127
in 0 channels
Get PRO
January '25
+165
in 0 channels
Get PRO
December '24
+199
in 0 channels
Get PRO
November '24
+192
in 0 channels
Get PRO
October '24
+191
in 0 channels
Get PRO
September '24
+224
in 0 channels
Get PRO
August '24
+262
in 0 channels
Get PRO
July '24
+275
in 0 channels
Get PRO
June '24
+316
in 0 channels
Get PRO
May '24
+278
in 0 channels
Get PRO
April '24
+304
in 0 channels
Get PRO
March '24
+300
in 0 channels
Get PRO
February '24
+243
in 0 channels
Get PRO
January '24
+207
in 0 channels
Get PRO
December '23
+178
in 0 channels
Get PRO
November '23
+214
in 0 channels
Get PRO
October '23
+172
in 0 channels
Get PRO
September '23
+163
in 0 channels
Get PRO
August '23
+162
in 0 channels
Get PRO
July '23
+130
in 0 channels
Get PRO
June '23
+175
in 0 channels
Get PRO
May '23
+166
in 0 channels
Get PRO
April '23
+208
in 0 channels
Get PRO
March '23
+167
in 0 channels
Get PRO
February '23
+176
in 0 channels
Get PRO
January '23
+211
in 0 channels
Get PRO
December '22
+192
in 0 channels
Get PRO
November '22
+241
in 0 channels
Get PRO
October '22
+234
in 0 channels
Get PRO
September '22
+234
in 0 channels
Get PRO
August '22
+236
in 0 channels
Get PRO
July '22
+270
in 0 channels
Get PRO
June '22
+228
in 0 channels
Get PRO
May '22
+240
in 0 channels
Get PRO
April '22
+228
in 0 channels
Get PRO
March '22
+301
in 0 channels
Get PRO
February '22
+173
in 0 channels
Get PRO
January '22
+218
in 0 channels
Get PRO
December '21
+194
in 0 channels
Get PRO
November '21
+162
in 0 channels
Get PRO
October '21
+160
in 0 channels
Get PRO
September '21
+150
in 0 channels
Get PRO
August '21
+188
in 0 channels
Get PRO
July '21
+149
in 0 channels
Get PRO
June '21
+201
in 0 channels
Get PRO
May '21
+125
in 0 channels
Get PRO
April '21
+2 206
in 0 channels
| Date | Subscriber Growth | Mentions | Channels | |
| 27 July | +1 | |||
| 26 July | +5 | |||
| 25 July | 0 | |||
| 24 July | 0 | |||
| 23 July | +3 | |||
| 22 July | +1 | |||
| 21 July | +4 | |||
| 20 July | +2 | |||
| 19 July | 0 | |||
| 18 July | +5 | |||
| 17 July | +3 | |||
| 16 July | +3 | |||
| 15 July | +1 | |||
| 14 July | +3 | |||
| 13 July | +2 | |||
| 12 July | +2 | |||
| 11 July | +1 | |||
| 10 July | +2 | |||
| 09 July | +1 | |||
| 08 July | +1 | |||
| 07 July | +2 | |||
| 06 July | +2 | |||
| 05 July | +1 | |||
| 04 July | +1 | |||
| 03 July | 0 | |||
| 02 July | +2 | |||
| 01 July | +2 |
Channel Posts
PostgreSQL 19 improves processing of text and CSV input with SIMD CPU instructions. SIMD allows a processor to perform the same operation on multiple pieces of data simultaneously.
The practical result may be faster ingestion for migrations, ETL pipelines, analytics systems, and large batch imports. Actual improvement will depend on the hardware, file format, storage system, constraints, and indexes.
5. LZ4 becomes the default TOAST compression method
PostgreSQL uses TOAST to manage values that are too large to fit conveniently inside a normal table row. PostgreSQL 19 changes the default TOAST compression method from
pglz to the generally faster lz4.
This is an important example of a database improvement that applications may benefit from without changing their SQL. Nevertheless, teams should evaluate compression ratio, CPU usage, and compatibility during upgrade testing.
ā ļø Should you upgrade now?
Noānot in production.
PostgreSQL 19 Beta 2 is a testing release. Features, behavior, and interfaces may still change before the final release, currently expected around September or October 2026.
A productive testing approach is to:
Restore a sanitized production backup into an isolated environment.
Replay representative queries and maintenance operations.
Compare execution plans and performance with your current version.
Test drivers, extensions, backup tools, and monitoring systems.
Report reproducible bugs or regressions to the PostgreSQL project.
Key lesson: A beta release is not merely an early download. It is an opportunity to discover compatibility issues, understand upcoming optimizer behavior, and prepare a safer future upgrade.
š PostgreSQL 19 Beta 2 announcement
š PostgreSQL 19 release notes
š Official beta-testing guidance
#PostgreSQL #SQL #Database #DatabaseAdministration #Performance #DataEngineering| 2 | š PostgreSQL 19 Beta 2: Five Changes Database Engineers Should Watch
PostgreSQL 19 Beta 2 was released on July 16, 2026. Although it is not intended for production use, it provides an excellent preview of improvements expected in the next major PostgreSQL release.
Here are five especially interesting developments:
1. Smarter optimization of NOT IN queries
PostgreSQL 19 can convert certain NOT IN predicates into more efficient anti joins when NULL values cannot occur.
SELECT c.customer_id
FROM customers AS c
WHERE c.customer_id NOT IN (
SELECT o.customer_id
FROM orders AS o
);
An anti join returns rows from the first input that have no match in the second input. It can perform much better than repeatedly evaluating a subquery.
However, remember the famous SQL NULL trap: if the subquery can return NULL, NOT IN may produce an unexpected result. A safer alternative is often:
SELECT c.customer_id
FROM customers AS c
WHERE NOT EXISTS (
SELECT 1
FROM orders AS o
WHERE o.customer_id = c.customer_id
);
Even with a smarter optimizer, understanding SQLās three-valued logic remains essential.
2. Parallel autovacuum workers
PostgreSQL relies on VACUUM to remove obsolete row versions and prevent transaction-ID problems. In PostgreSQL 19, autovacuum can use parallel workers, potentially accelerating maintenance on large tables.
The feature is controlled globally and can also be configured per table. It should be particularly useful for large, heavily updated databasesābut more workers also mean greater CPU and I/O demand. Administrators should benchmark it under realistic workloads rather than immediately selecting the highest possible value.
3. Online checksum management
Data checksums help PostgreSQL detect corrupted database pages. Previously, enabling or disabling them required shutting down the cluster and using the pg_checksums utility.
PostgreSQL 19 introduces support for changing checksum status while the server is online. This can reduce operational disruption, although administrators still need to plan carefully and monitor the process.
Checksums detect corruption; they do not repair it. Reliable backups, restore testing, storage monitoring, and replication remain necessary.
4. Faster CSV and text imports
COPY FROM is PostgreSQLās primary high-speed bulk-loading mechanism:
COPY sales
FROM '/data/sales.csv'
WITH (FORMAT csv, HEADER true); | 367 |
| 3 | https://www.mssqltips.com/sqlservertip/11657/softmax-function-in-sql-server/ | 248 |
| 4 | https://www.mssqltips.com/sqlservertip/8290/sql-server-2025-new-features/ | 232 |
| 5 | https://www.mssqltips.com/sqlservertip/11711/visual-studio-code-with-github-copilot/ | 218 |
| 6 | https://www.mssqltips.com/sqlservertip/7218/dark-mode-ssms-configuration/ | 254 |
| 7 | https://www.mssqltips.com/sqlservertip/11526/sql-parameter-sniffing-fix-with-a-covering-index/ | 189 |
| 8 | https://www.mssqltips.com/sqlservertip/8114/sql-server-query-store-for-query-performance-history/ | 171 |
| 9 | https://www.mssqltips.com/sqlservertip/7688/sql-scripts-monitoring-current-activity-blocking-performance/ | 178 |
| 10 | https://www.mssqltips.com/sqlservertip/4717/what-is-sql-server-alwayson/ | 143 |
| 11 | https://www.mssqltips.com/sqlservertip/11504/data-protection-with-tokenization-in-sql-server/ | 145 |
| 12 | https://www.mssqltips.com/sqlservertip/7429/sql-triggers-for-inserts-updates-and-deletes-on-a-table/ | 140 |
| 13 | https://www.mssqltips.com/sqlservertip/11705/sql-server-ha-and-dr-with-dxenterprise/ | 154 |
| 14 | https://www.mssqltips.com/sqlservertip/11617/ssms-query-hint-recommendation-tool/ | 164 |
| 15 | https://www.mssqltips.com/sqlservertip/6244/microsoft-sql-server-data-warehouse-data-quality-cleansing-verification-and-matching/ | 176 |
| 16 | https://www.mssqltips.com/sqlservertip/6307/how-to-stop-and-start-sql-server-services/ | 181 |
| 17 | https://www.mssqltips.com/sqlservertip/5855/update-statistics-for-all-tables-and-databases-in-a-sql-server-instance/ | 179 |
| 18 | https://www.mssqltips.com/sqlservertip/6975/enable-disable-full-text-search-sql-server-database/ | 185 |
| 19 | https://www.dreamfactory.com/connectors/sql-server/?utm_source=mssqltips | 205 |
| 20 | https://www.mssqltips.com/sqlservertip/11538/json-index-in-sql-server/ | 323 |
