Всё о GUC по порядку: enable_incremental_sort https://sql-ex.ru/blogs/?/Vsjo_o_GUC_po_porJadku_enable_incremental_sort.html Автор: Christophe Pettus, All Your GUCs in a Row: enable_incremental_sort (https://postgr.es/p/9ny) Действительно хорошая функциональность скрывается за этим переключателем, что делает его одним из наиболее интересных параметров семейства enable_* для понимания, — и одним из немногих, у кого е…

Channel
SQL-Ex
@sqlexercises
On this record: Growth · Engagement · Reactions · Posts · Cite this entry
1,994subscribers
-12 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001710588779 |
|---|---|
| Type | Channel |
| Username | @sqlexercises |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/sqlexercises |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 08:29 | 1,994 | -5 |
| 18 Aug 2026, 19:04 | 1,999 | -1 |
| 15 Aug 2026, 20:24 | 2,000 | -2 |
| 12 Aug 2026, 02:08 | 2,002 | -3 |
| 8 Aug 2026, 16:55 | 2,005 | -1 |
| 7 Aug 2026, 23:45 | 2,006 | no change |
| 7 Aug 2026, 23:38 | 2,006 | first reading |
Engagement
20 posts held, back to 21 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 6.87%
- avg views ÷ 1,994 subscribers
- Avg views / post
- 137
- 13 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 13
- of 20 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 20 (21 July 2026 – 7 August 2026) |
| Views total | 1,781 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 23:45 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Reaction mix
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.0% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 1 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 1reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 21 July 2026 to 7 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
Всё о GUC по порядку: enable_hashjoin https://sql-ex.ru/blogs/?/Vsjo_o_GUC_po_porJadku_enable_hashjoin.html Автор: Christophe Pettus, All Your GUCs in a Row: enable_hashjoin (https://sql-ex.ru/blogs/?/Vsjo_o_GUC_po_porJadku_enable_hashjoin.html) Первый из трёх переключателей стратегий соединения, поэтому прежде чем перейти к параметру, — один абзац о том, внутри чего он находится: в PostgreSQL есть ровно три способ…
pg_stats: как работает внутренняя статистика Postgres https://sql-ex.ru/blogs/?/pg_stats_kak_rabotaet_vnutrennJaJa_statistika_Postgres.html Автор: Richard Yen (https://richyen.com/), pg_stats: How Postgres Internal Stats Work (https://richyen.com/postgres/2026/06/22/pg_stats_how_postgres_internal_stats_work.html) Недавно мне выпала честь выступить на POSETTE 2026 с докладом о pg_stats и о том, как работает внутренн…
Всё о GUC по порядку: enable_hashagg https://sql-ex.ru/blogs/?/Vsjo_o_GUC_po_porJadku_enable_hashagg.html Автор: Christophe Pettus, All Your GUCs in a Row: enable_hashagg (https://postgr.es/p/9nt) Самый значимый переключатель в семействе enable_*, потому что поведение, которым он управляет, изменилось в PostgreSQL 13 таким образом, что некоторые запросы замедлились при обновлении, — и enable_hashagg стал на некотор…
Всё о GUC по порядку: enable_gathermerge https://sql-ex.ru/blogs/?/Vsjo_o_GUC_po_porJadku_enable_gathermerge.html Автор: Christophe Pettus, All Your GUCs in a Row: enable_gathermerge (https://postgr.es/p/9nm) Переключатель параллельных запросов и один из наиболее интересных членов семейства enable_* для переключения, потому что то, что он отключает, имеет чистое, предсказуемое замещение. По умолчанию включён, конте…
Оптимизация полиморфных ассоциаций в PostgreSQL https://sql-ex.ru/blogs/?/OptimizaciJa_polimorfnyh_associacij_v_PostgreSQL.html Автор: Андрей Лепихов,Optimising Polymorphic Associations in PostgreSQL (https://postgr.es/p/9mA) Недавно я исследовал (https://open.substack.com/pub/danolivo/p/on-polymorphic-associations-in-postgres?r=34q1yy&utm_campaign=post-expanded-share&utm_medium=web), насколько распространены полим…
Всё о GUC по порядку: enable_distinct_reordering и enable_group_by_reordering https://sql-ex.ru/blogs/?/Vsjo_o_GUC_po_porJadku_enable_distinct_reordering_i_enable_group_by_reordering.html Автор: Christophe Pettus, All Your GUCs in a Row: enable_distinct_reordering and enable_group_by_reorderin (https://postgr.es/p/9nj)g Два самых молодых члена семейства enable_* и естественная пара: оба позволяют планировщику переу…
IDENTITY или SEQUENCE в SQL Server – что использовать? https://sql-ex.ru/blogs/?/IDENTITY_ili_SEQUENCE_v_SQL_Server__chto_ispolzovat.html Пересказ статьи Greg Low. IDENTITY vs SEQUENCE in SQL Server – which should you use? (https://www.red-gate.com/simple-talk/databases/sql-server/identity-vs-sequence-in-sql-server-which-should-you-use/) Автоматически генерируемые числовые ключи имеются повсюду в реляционных базах …
Новости за 2026-07-25 - 2026-07-31 https://sql-ex.ru/blogs/?/Novosti_za_2026-07-25_-_2026-07-31.html § С целью защиты от подгонки автор (https://sql-ex.ru/users_page.php?uid=791796) внес косметические изменения в условие (и решение) задачи 242 § Популярные темы недели на форуме Топик Сообщений Просмотров 242 (SELECT) (https://sql-ex.ru/forum/forum.php?F=1&N=242) 9 3 181 (SELECT) (https://sql-ex.ru/forum/forum.…
Всё о GUC по порядку: enable_indexscan и enable_bitmapscan https://sql-ex.ru/blogs/?/Vsjo_o_GUC_po_porJadku_enable_indexscan_i_enable_bitmapscan.html Автор: Christophe Pettus, All Your GUCs in a Row: enable_indexscan and enable_bitmapscan (https://postgr.es/p/9nd) Ещё два переключателя планировщика из семейства enable_*, и они идут вместе, потому что то, что они отключают, в обоих случаях является индексом, — разни…
Проблемы параллелизма SQL Server с планами одновременно выполняющихся запросов https://sql-ex.ru/blogs/?/Problemy_parallelizma_SQL_Server_s_planami_odnovremenno_vypolnJajuwihsJa_zaprosov.html Пересказ статьи Mehdi Ghapanvari. SQL Server Concurrency Issues with Parallel Query Plans (https://www.mssqltips.com/sqlservertip/11619/sql-server-concurrency-issues-with-parallel-query-plans/) Параллелизм может уменьшить спос…
Ответы на вопросы относительно удаленных столбцов https://sql-ex.ru/blogs/?/Otvety_na_voprosy_otnositelno_udalennyh_stolbcov.html Пересказ статьи Cláudio Silva. Answering Questions On Dropped Columns (https://www.sqlservercentral.com/articles/answering-questions-on-dropped-columns) В этой статье я отвечу на пару вопросов из предыдущих публикаций об удалении столбцов. Если вы не читали предыдущих постов по этой тем…
Showing the 12 most recent of 20 posts we hold for @sqlexercises. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 22 August 2026 — this entry's latest reading, not the date you are reading this.
“SQL-Ex” (@sqlexercises), 1,994 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/sqlexercises.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.