Channel

Greengage DB

@greengagedb

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

979subscribers

+0 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID	-1002182285857
Type	Channel
Username	@greengagedb
Created	Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	6 August 2026
Last confirmed live	14 August 2026
Measurements held	2
Confirmed unchanged	2 times, most recently 14 August 2026
On Telegram	t.me/greengagedb

Growth

2 measurements taken within a single day. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 978–980 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
7 Aug 2026, 08:25	979	no change
6 Aug 2026, 22:46	979	first reading

Engagement

18 posts held, back to 26 September 2025 — 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: 160.4%; avg views ÷ 979 subscribers
Avg views / post: 1,570; 2 posts measured
Reaction rate: 2.58%; reactions ÷ views · ER floor
Posts in window: 2; of 18 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.

What these figures were computed from
Window	Rolling 30 days · latest post in window 24 July 2026
Posts held	18 (26 September 2025 – 24 July 2026)
Views total	3,140
Reactions total	81
Forwards / comments	not exposed by the public surface — not measured, not estimated
Readings taken	6 Aug 2026, 22:46 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

773 reactions across 18 posts, in 10 distinct kinds. The most used accounts for 56.3% of them.

Every reaction kind recorded on the sample, most used first
Reaction	Count	Share
🔥	435	56.3%
👍	138	17.9%
❤	124	16.0%
⚡	16	2.07%
☃	14	1.81%
❤‍🔥	13	1.68%
👏	11	1.42%
😍	9	1.16%
🤩	9	1.16%
👌	4	0.517%

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 18 of the 18 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 773reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 26 September 2025 to 24 July 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

24 Jul 2026, 15:46 UTC≈1,300 views37 reactionsread 6 August 2026

Photo

Всем пятничный привет, на связи Дмитрий Плужников ☕ 🔖 На этой неделе мы выпустили релиз Greengage DB 7.5.0. За полгода, прошедшие с момента выпуска предыдущего релиза семерки, командой проделана большая работа. С полным списком изменений, вошедших в релиз, можно ознакомиться в списке продуктовых релизов. ☄ Пожалуй, наиболее ожидаемой фичей в Greengage DB 7.5.0 стала первая версия утилиты ggrebalance, о разработке к…

🔥15❤12👍10

17 Jul 2026, 12:32 UTC≈1,840 views44 reactionsread 6 August 2026

Photo

Всем пятничный привет, на связи Дмитрий Плужников ☕ За прошедшие две недели у нас вышло сразу несколько важных обновлений технического блога и документации Greengage DB и PXF: 1⃣Опубликована вторая часть из цикла статей Александра Кондакова, посвященных утилите ggrebalance. В новой статье рассматривается перебалансировка сегментов Greengage-кластера после shrink-операций, а также в сценариях декомиссии и добавлени…

🔥23❤12😍9

26 Jun 2026, 13:09 UTC879 views37 reactionsread 6 August 2026

Photo

Всем пятничный привет, на связи Дмитрий Плужников ☕ Я к вам с новостями нашего проекта: ✅В техническом блоге Greengage DB опубликована новая статья от нашего архитектора Ольги Сергеевой – "Мажорное обновление Greengage с помощью pg_upgrade и ggupgrade". Статья включает: 🔜Обзор утилиты pg_upgrade и специфики ее использования для Greengage DB. 🔜Пример пошагового обновления кластера Greengage DB 6 до версии 7 на Ubu…

🔥21👍9❤7

29 May 2026, 12:09 UTC≈2,610 views38 reactionsread 6 August 2026

Photo

Всем пятничный привет, на связи Дмитрий Плужников ☕ У меня для вас сразу 2 новости: 1️⃣ Мы опубликовали первую статью из новой серии об утилите ggrebalance - "Part 1. Shrink". В материале мы рассказываем про: 🔜архитектру утилиты ребаланса кластера; 🔜как устроен механизм shrink; 🔜как обеспечивается безопасность перераспределения данных; 🔜результаты тестов производительности. Скоро она также будет опубликована на б…

🔥18👍11❤9

15 May 2026, 14:20 UTC≈2,490 views44 reactionsread 6 August 2026

Photo

Всем пятничный привет, на связи команда Greengage ☕ 🔖 В начале недели у нас вышло небольшое, но важное обновление документации Greengage DB. 🔜 Мы выпустили две новые статьи в разделе "Администрирование СУБД -> Обновление": ✅ Обновление кластера Greengage DB - описание общей процедуры обновления кластера Greengage DB между мажорными версиями, включаю подготовку и непосредственно саму миграцию данных. ✅ Несовместимос…

👍19🔥16❤9

30 Apr 2026, 13:21 UTC≈2,520 views32 reactionsread 6 August 2026

Photo

Коллеги, всем привет! На связи Дмитрий Плужников ☕️ Помните, мы рассказывали о добавлении поддержки Greengage DB в DBeaver и обещали продолжить интеграции с другими популярными клиентами? Выполняем обещание 👍 Теперь Greengage DB поддерживается в Beekeeper Studio - это современный кроссплатформенный SQL-клиент с открытым исходным кодом. Документация по подключению доступна на их сайте. Следите за новостями! 😉 В…

🔥17👍10⚡5

22 Apr 2026, 14:52 UTC≈2,940 views56 reactionsread 6 August 2026

Photo

Всем привет, на связи Дмитрий Плужников☕️ 📣 Я к вам с новостями нашего проекта Greengage DB: 🔜мы завершили большой пласт работ по апгрейду мажорной версии постгреса, результатами которых частично поделимся уже этим летом 🔜основную информацию расскажем на нашей большой осенней конференции ArenaTech - анонс которой будет чуть позже 🔜также будет выпущен ряд статей с результатами исследований на нашем блоге на Хабр 🔥 …

🔥28👍17❤11

13 Mar 2026, 13:35 UTC≈1,770 views51 reactionsread 6 August 2026

Photo

👋 Всем пятничный привет! 🔥Сегодня вышел релиз Greengage DB 6.30.1, куда вошли следующие ключевые изменения: 🔜поддержка Ubuntu 24.04; 🔜одновременная поддержка python2 и python3; 🔜поддержка ресурсных групп для сессий параллельного извлечения данных и их отображение в pg_stat_activity; 🔜добавлено новое расширение temp_tables_stat для мониторинга временных таблиц. 🔖Также мы выпустили первый релиз greengage-exporter - …

🔥29❤11👏11

11 Mar 2026, 10:55 UTC≈1,010 views33 reactionsread 6 August 2026

Photo

Всем привет 👋 Мы актуализировали roadmap Greengage DB и зафиксировали ключевые направления развития продукта на ближайшие этапы. Стоит отметить, что в нем указаны не все задачи в нашей работе. Некоторые фичи требуют дополнительного исследования и будут включены в роадмэп позже. Тем не менее, посмотреть обновленную дорожную карту Greengage DB вы всегда можете на сайте проекта. 🚀 P.S. Уже на этой неделе мы выпустим…

🔥21❤8👌4

13 Feb 2026, 08:31 UTC≈1,620 views45 reactionsread 6 August 2026

Photo

Всем пятничный привет, на связи Дмитрий Плужников ☕️ У нас сразу две новости. 1️⃣ Программа перспективных C-разработчиков Мы продолжаем искать студентов старших курсов технических ВУЗов и начинающих разработчиков, которым интересно: — участвовать в Open-Source проекте — влиять на продукт, которым реально пользуются компании — заниматься промышленной C-разработкой — прокачать системное мышление — стать частью наше…

🔥25❤11🤩9

29 Dec 2025, 14:45 UTC≈1,480 views49 reactionsread 6 August 2026

Photo

Всем привет! На связи Дмитрий Плужников, CTO Arenadata, с финальными новостями уходящего года 👋 Во-первых, под конец года мы обновили нашу документацию Greengage DB 🌳 🔜Существенно расширена документация по Greengage DB 6: добавлены новые материалы про работу с данными, администрирование СУБД, интеграцию с внешними системами (в том числе примеры использования коннектора PXF JDBC). Добавлена первая архитектурная ста…

🔥29☃14❤6

26 Dec 2025, 15:51 UTC≈1,260 views30 reactionsread 6 August 2026

Photo

📣 Всем привет, на связи Антон Коваленко, Head of product marketing Arenadata. У меня есть новости, достойные вашего внимания. Команда DataCatalog, в рамках очередного обновления 0.8.5, выпустила коннектор для Greengage DB 🌳 🔜Новый коннектор, подобно аналогу для Arenadata DB (ADB), поддерживает фреймворк PXF (Platform Extension Framework); 🔜Метаданные Greengage интегрируются в каталог данных Arenadata Catalog; 🔜Функ…

🔥18👍8❤4

Showing the 12 most recent of 18 posts we hold for @greengagedb. 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.

Citation-graph rank

Citation-graph rank — 181,912 of 1,480,688entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Arenadata
@arenadata · 3,2133 posts SQLClub
@sqlclub_ru · 1,4451 post

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 1 registered channel — 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.

SQLClub
@sqlclub_ru · 1,4451 post

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.

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 7 August 2026 — this entry's latest reading, not the date you are reading this.

“Greengage DB” (@greengagedb), 979 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/greengagedb.

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.