🖥 pg-delta строит изменения PostgreSQL из описания желаемой схемы В проекте растёт история SQL-миграций. Чтобы понять текущее устройство базы, приходится восстанавливать его по десяткам файлов. При декларативном подходе вы храните желаемую схему в SQL-файлах. Инструмент сравнивает её с текущим состоянием и готовит изменения для перехода. В разборе Declarative Schemas 2.0 показана работа pg-delta: от описания объек…

Channel
Сохранёнки программиста
@prog_stuff
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
6,453subscribers
-124 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001478068288 |
|---|---|
| Type | Channel |
| Username | @prog_stuff |
| Description | Заметки и ссылки на будущее, чтобы изучить когда будет время. Разместить рекламу: @tproger_sales_bot Правила общения: https://tprg.ru/rules Другие каналы: @tproger_channels Другие наши проекты: https://tprg.ru/med |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/prog_stuff |
Topic
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 98% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Nov 2026, 09:06 | 6,453 | -12 |
| 5 Nov 2026, 19:57 | 6,465 | -3 |
| 2 Nov 2026, 11:58 | 6,468 | -1 |
| 30 Oct 2026, 21:59 | 6,469 | -3 |
| 28 Oct 2026, 02:47 | 6,472 | -14 |
| 24 Oct 2026, 20:08 | 6,486 | -11 |
| 21 Oct 2026, 20:11 | 6,497 | -6 |
| 19 Oct 2026, 01:30 | 6,503 | -5 |
| 15 Oct 2026, 17:07 | 6,508 | -4 |
| 12 Oct 2026, 14:31 | 6,512 | -2 |
| 5 Oct 2026, 17:01 | 6,514 | -9 |
| 28 Sept 2026, 09:56 | 6,523 | -10 |
| 18 Sept 2026, 21:18 | 6,533 | -3 |
| 11 Sept 2026, 05:16 | 6,536 | -11 |
| 6 Sept 2026, 14:17 | 6,547 | +7 |
| 2 Sept 2026, 04:24 | 6,540 | +8 |
| 30 Aug 2026, 00:37 | 6,532 | -7 |
| 27 Aug 2026, 02:45 | 6,539 | -9 |
| 24 Aug 2026, 04:05 | 6,548 | -4 |
| 20 Aug 2026, 16:52 | 6,552 | first reading |
Engagement
55 posts held, back to 14 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 17 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 5.06%
- avg views ÷ 6,453 subscribers
- Avg views / post
- 327
- 32 posts measured
- Reaction rate
- 0.181%
- reactions ÷ views · ER floor
- Posts in window
- 32
- of 55 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. It is computed over the 5 of 32 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 9 November 2026 |
|---|---|
| Posts held | 55 (14 July 2026 – 9 November 2026) |
| Views total | 10,456 |
| Reactions total | 3 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Nov 2026, 17:27 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.
What this channel posts
- Photos
- ≈1,280
- Videos
- ≈59
- Links
- ≈2,000
Lifetime counters from Telegram’s own channel header, read 9 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Reaction mix
37 reactions across 23 posts, in 11 distinct kinds. The most used accounts for 35.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 13 | 35.1% | |
| ❤ | 7 | 18.9% | |
| 🤯 | 5 | 13.5% | |
| 💊 | 3 | 8.11% | |
| ❤🔥 | 2 | 5.41% | |
| 🔥 | 2 | 5.41% | |
| 👏 | 1 | 2.70% | |
| 💯 | 1 | 2.70% | |
| 😁 | 1 | 2.70% | |
| 😇 | 1 | 2.70% | |
| 🤪 | 1 | 2.70% |
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 25 of the 55 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 37 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 55 most recent posts we hold, published 14 July 2026 to 9 November 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.
Advertising
- Ad load
- 1.82%
- 1 of 55 posts carry an ad marker
- Regulatory tokens
- 1
- posts carrying an erid · 1 distinct token
- Median views · ads
- 549
- over 1 measured post
- Median views · rest
- 370
- over 54 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2W5zFHGdLk9 | 1 | 14 July 2026 | 14 July 2026 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 55 most recent posts we hold, published 14 July 2026 to 9 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 32 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🖥 OrioleDB использует undo-журнал для хранения предыдущих версий строк PostgreSQL В PostgreSQL частые обновления создают старые версии строк. Их очистка и накопление влияют на размер таблиц и работу базы. OrioleDB предлагает другой механизм хранения: прежние версии данных размещаются в undo-журнале. Проект также использует собственную организацию таблиц и индексов. В разборе публичной беты показано, как движок раб…
🖥 Проверка CVE в реестре помогает отсеять выдуманные уязвимости из ИИ-ревью ИИ-ревьюер нашёл опасную проблему, сослался на CVE и предложил исправление. При проверке выяснилось, что такого идентификатора вообще нет. В кейсе Docker разобраны две части защиты. Среда ограничивает возможности агента: доступ к файлам, сети и секретам. Отдельная проверка сверяет упомянутые CVE с реестром NVD. В примере отчёт остаётся тек…
🖥 Cloudflare сократила расход памяти на сборку DNS-зон на 85% Изменение одной настройки могло запускать полную пересборку DNS-зоны с миллионами записей. На крупных зонах такая работа занимала время и создавала высокую нагрузку на память. Cloudflare добавила планировщик сборки, который определяет минимальный безопасный объём изменений. Для подходящих операций система обрабатывает только необходимую часть зоны. На с…
😇1
Фоновая очистка GitHub исчерпала подключения к общей базе Задача очистки следила за отставанием реплик и замедляла запись при росте задержки. Нагрузку на основной сервер она не учитывала. В результате база достигла лимита подключений, а зависимые запросы начали сбоить. В разборе сентябрьского инцидента GitHub описаны ещё два фактора: вызовы базы долго ждали без быстрого тайм-аута, а повторные попытки создания токен…
ИИ-агенту нужны актуальные правила Selenium, чтобы писать устойчивые тесты Агент добавил sleep(5), скопировал длинный XPath и подключил лишнюю библиотеку для драйвера. Тест проходит локально, а в CI периодически падает. Команда Selenium разобрала повторяющиеся ошибки агентов и подготовила рекомендации для файлов инструкций проекта. Агенту стоит передать версию Selenium, актуальную документацию и рабочие примеры. На…
Токен Supabase можно ограничить одним проектом и нужными действиями Скрипту генерации типов нужен доступ к структуре базы. Токен с правами на весь аккаунт заодно открывает ему другие проекты и операции. В Supabase можно выбрать ресурсы, разрешения и срок действия токена. Для чтения базы одного проекта достаточно выделить этот проект и включить соответствующее разрешение. Скрипту деплоя можно выдать отдельный токен.…
Профиль Go показывает горутины, которые навсегда застряли в ожидании Функция запустила несколько обработчиков и собирает ответы через канал. Первый обработчик вернул ошибку, функция завершилась. Остальные продолжают отправлять результаты в канал, который уже никто не читает. Такие горутины удерживают память и накапливаются при повторных вызовах. В Go 1.27 появился профиль goroutineleak, который обнаруживает часть п…
Облачные PostgreSQL можно сравнить на воспроизводимой нагрузке При выборе базы полезно видеть вместе пропускную способность, задержки и стоимость. Для этого в DBArena публикуют конфигурации и исходные результаты тестов, которые можно повторить самостоятельно. Проект финансирует Supabase. В первом наборе сравнивают Supabase, Amazon RDS и Google Cloud SQL на PostgreSQL 17. Есть два сценария: данные помещаются в памят…
Возможность отката стоит закладывать при проектировании функции Новый формат записали на диск, внутренний метод открыли внешним клиентам — вокруг решения начинают появляться зависимости. Позже его изменение потребует миграции данных и согласования с пользователями API. В Google Testing Blog собрали приёмы, которые сохраняют возможность передумать: — включать новую логику через флаг; — ограничивать доступ к API, по…
Go 1.27 сохраняет HTTP-соединение после закрытия непрочитанного ответа Клиенту нужен только статус ответа, поэтому он вызывает resp.Body.Close() и идёт дальше. В Go до версии 1.27 непрочитанное тело HTTP/1-ответа мешало повторно использовать соединение. Следующий запрос мог снова тратить время на TCP и TLS. В Go 1.27 транспорт дочитывает остаток в фоне: на это выделено до 50 мс и 256 КБ. Если тело удалось прочитать…
😁1
SQL-запросы и ход расследования можно хранить рядом с кодом Нашли причину сбоя, отправили вывод в чат, закрыли вкладки. Через месяц похожая проблема возникает снова, и запросы приходится собирать заново. В Supabase появились Explorer и Notebooks: в одном документе можно сохранить запросы к базе и логам, графики и заметки о проверках. Файл хранится в папке supabase, попадает в Git и проходит обычное ревью. При повто…
Showing the 12 most recent of 55 posts we hold for @prog_stuff. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
Handles this channel named that no longer answer
- Dead references
- 2
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 2
- vacant every time we have ever looked
@prog_stuff named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 8 August 2026 – 8 August 2026
named in 1 post, 8 August 2026 – 8 August 2026
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@ProgrammingTip · 45,887
Telegram ranks this channel #15 of 73 here — alongside 72 others — read 27 August 2026
@zen_of_python · 18,630
Telegram ranks this channel #17 of 91 here — alongside 90 others — read 5 October 2026
@tproger_web · 22,155
Telegram ranks this channel #24 of 96 here — alongside 95 others — read 20 September 2026
@tproger · 78,009
Telegram ranks this channel #27 of 95 here — alongside 94 others — read 19 August 2026
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 9 November 2026 — this entry's latest reading, not the date you are reading this.
“Сохранёнки программиста” (@prog_stuff), 6,453 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/prog_stuff.
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.