Telegram RegisterThe public register of Telegram
Telegram profile photo for Базы данных (Data Base)

Channel

Базы данных (Data Base)

@database_info

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Citations · Telegram's recommendations · Cite this entry

8,021subscribers

-72 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-1001390705566
TypeChannel
Username@database_info
DescriptionБазы данных (Data Base). По всем вопросам @evgenycarter
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live11 November 2026
Measurements held25
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/database_info

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 99% 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

8,0218,0958,0586 August 2026 — 8,093 subscribers7 August 2026 — 8,095 subscribers10 August 2026 — 8,087 subscribers13 August 2026 — 8,083 subscribers16 August 2026 — 8,090 subscribers19 August 2026 — 8,091 subscribers26 August 2026 — 8,083 subscribers29 August 2026 — 8,079 subscribers1 September 2026 — 8,082 subscribers5 September 2026 — 8,080 subscribers10 September 2026 — 8,070 subscribers14 September 2026 — 8,058 subscribers18 September 2026 — 8,059 subscribers29 September 2026 — 8,051 subscribers5 October 2026 — 8,050 subscribers12 October 2026 — 8,043 subscribers15 October 2026 — 8,040 subscribers19 October 2026 — 8,028 subscribers21 October 2026 — 8,030 subscribers27 October 2026 — 8,033 subscribers30 October 2026 — 8,030 subscribers2 November 2026 — 8,027 subscribers4 November 2026 — 8,025 subscribers8 November 2026 — 8,027 subscribers11 November 2026 — 8,021 subscribers6 August 202611 November 2026
25 measurements spanning 97 days, net -72. 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 8,010–8,106 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 25
Measured (UTC)SubscribersChange
11 Nov 2026, 12:108,021-6
8 Nov 2026, 03:598,027+2
4 Nov 2026, 23:158,025-2
2 Nov 2026, 01:088,027-3
30 Oct 2026, 06:558,030-3
27 Oct 2026, 11:468,033+3
21 Oct 2026, 23:318,030+2
19 Oct 2026, 00:018,028-12
15 Oct 2026, 22:568,040-3
12 Oct 2026, 20:368,043-7
5 Oct 2026, 23:408,050-1
29 Sept 2026, 02:198,051-8
18 Sept 2026, 18:158,059+1
14 Sept 2026, 02:368,058-12
10 Sept 2026, 15:198,070-10
5 Sept 2026, 18:168,080-2
1 Sept 2026, 09:538,082+3
29 Aug 2026, 05:248,079-4
26 Aug 2026, 11:368,083-8
19 Aug 2026, 19:138,091first reading

Engagement

49 posts held, back to 19 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 38 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
9.29%
avg views ÷ 8,021 subscribers
Avg views / post
745
13 posts measured
Reaction rate
0.671%
reactions ÷ views · ER floor
Posts in window
13
of 49 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
WindowRolling 30 days · latest post in window 11 November 2026
Posts held49 (19 July 2026 – 11 November 2026)
Views total9,687
Reactions total65
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Nov 2026, 01:59 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
684
Videos
478
Links
705

Lifetime counters from Telegram’s own channel header, read 12 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
1h 18m
Average length
26m 05s

Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

225 reactions across 47 posts, in 11 distinct kinds. The most used accounts for 53.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍12153.8%
🔥5825.8%
❤2611.6%
😁94.00%
👎31.33%
💯20.889%
🤡20.889%
🌚10.444%
👏10.444%
💩10.444%
🖕10.444%

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

Measured over the 49 most recent posts we hold, published 19 July 2026 to 11 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
4.08%
2 of 49 posts carry an ad marker
Regulatory tokens
2
posts carrying an erid · 2 distinct tokens
Median views · ads
888
over 2 measured posts
Median views · rest
827
over 47 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.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2W5zFJF5Fkm123 July 202623 July 2026
2W5zFJmnYQ918 October 20268 October 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 49 most recent posts we hold, published 19 July 2026 to 11 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: 1 of 13 posts held from the last 30 days (7.69%) 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).

11 Nov 2026, 07:28 UTC310 views4 reactionsread 12 November 2026
Photo

Антипаттерн: N+1 запросов и как его избежать Что такое N+1? При выборке связанных данных ORM (или вручную) сначала делается 1 запрос за основными записями, а потом N дополнительных - по одной для каждой записи, чтобы получить связанные объекты. Например, получить 10 пользователей и для каждого — список их заказов ⇒ 1 запрос к users + 10 запросов к orders. 🚩 # SQLAlchemy-пример “N+1”: users = session.query(User).al…

👍3❤1

10 Nov 2026, 04:51 UTC445 views2 reactionsread 12 November 2026
Photo

Мини-гайд: Как не превратить индексы в PostgreSQL в ловушку для производительности Добавил пару-тройку индексов — стало быстрее? Отлично! Но помни: индексы — это не бесплатная магия. Вот что важно учитывать: 1. Индексы ускоряют SELECT, но тормозят INSERT/UPDATE/DELETE. Каждая модификация данных требует обновления всех связанных индексов. Чем их больше — тем медленнее запись. 2. Следи за “мертвыми” индексами. …

👍2

9 Nov 2026, 05:48 UTC489 views4 reactionsread 12 November 2026
Photo

🔗 Сравнение: Типы JOIN в SQL и когда их применять Зачем понимать JOIN’ы? Правильный выбор типа соединения таблиц позволяет получать необходимые данные эффективно и избегать неожиданных «пустых» или дублирующихся строк. 1. Основные типы JOIN и их поведение INNER JOIN Возвращает только строки, у которых есть совпадения в обеих таблицах. Когда нужно только пересечение данных. LEFT JOIN Берёт все строки из левой таб…

👍3❤1

6 Nov 2026, 07:09 UTC695 views8 reactionsread 12 November 2026
Photo

❌ Антипаттерн: булевы значения как строки В таблице users встречал такое: is_active VARCHAR(5) -- значения 'true' или 'false' На первый взгляд — ерунда. На практике: – нет валидации: можно вставить 'tru', 'yes', '0', – медленнее сравнение, чем у BOOLEAN, – больше места в хранилище, – сложно агрегировать и строить аналитику. 🔧 Как надо: is_active BOOLEAN DEFAULT true – Экономия места (1 байт против 5 и больш…

👍3🔥3❤2

5 Nov 2026, 08:57 UTC707 views7 reactionsread 12 November 2026
Photo

🔧 Mini-гайд: ускоряем JOIN-ы в больших таблицах JOIN-ы - мощный инструмент SQL, но на больших объёмах данных могут стать узким горлышком. Вот 5 проверенных способов ускорить их: 1. Индексы по ключам соединения Без индекса - каждый JOIN превращается в полный перебор. ➤ Пример: CREATE INDEX idx_user_id ON orders(user_id); 2. Ограничь объём данных до JOIN-а Фильтруй и агрегируй данные до объединения.…

👍3🔥3❤1

5 Nov 2026, 07:02 UTC657 views4 reactionsread 12 November 2026
Photo

Pghero Панель управления производительностью для Postgres https://github.com/ankane/pghero 📲 Мы в MAX #db 👉 @database_info

👍4

30 Oct 2026, 07:03 UTC981 views4 reactionsread 12 November 2026
Photo

Антипаттерн: SELECT * - удобно, но опасно Использовать SELECT * - значит звать всех на вечеринку, даже если звал только двоих. Почему это плохо: 🔹 Излишняя нагрузка на сеть и СУБД - выбираются все столбцы, включая ненужные. 🔹 Проблемы с индексами - СУБД может не использовать покрывающий индекс. 🔹 Ломается при изменении схемы - добавил столбец → внезапно изменилось поведение приложения. 🔹 Сложнее читать и поддержива…

👍4

27 Oct 2026, 20:05 UTC945 views8 reactionsread 12 November 2026
Video

Postgres против MySQL. Postgres спроектирован как единая, целостная система, и этот архитектурный подход определяет принципы работы всех остальных компонентов. Данные хранятся в виде «кучи» (heap), где могут одновременно существовать несколько версий одной и той же строки. При обновлении создаются новые версии, а старые сохраняются до тех пор, пока не будут удалены в процессе очистки (VACUUM). Механизм MVCC (многов…

👍4🔥4

27 Oct 2026, 05:02 UTC806 views4 reactionsread 12 November 2026
Photo

🛑 Антипаттерн: "Списки через запятую" в базе данных Признайтесь, у каждого был соблазн сделать это. У вас есть сущность (например, User), и нужно сохранить список их ролей или IDs купленных товаров. Создавать отдельную таблицу кажется оверхедом, и вы решаете: "А, запишу просто строкой через запятую". В БД это выглядит так: role_ids: "1,4,12" Почему это бомба замедленного действия и как это лечить? Давайте разбират…

🔥3👍1

23 Oct 2026, 09:12 UTC829 views5 reactionsread 12 November 2026
Photo

PostgreSQL или MySQL? Один из самых частых вопросов от разработчиков и DevOps - “Что лучше: PostgreSQL или MySQL?”. Давай без фанатизма, просто по фактам 👇 🔷 PostgreSQL: 🔵Поддержка JSONB с индексами - почти как NoSQL внутри SQL 🔵CTE, оконные функции, полнотекстовый поиск - топ для аналитики 🔵Расширяемость: можно писать свои типы, функции, операторы 🔵Хорош для сложных запросов, аналитики, геоданных (PostGIS) 🔻 Мин…

👍2💯2🌚1

23 Oct 2026, 04:29 UTC763 views4 reactionsread 12 November 2026
Photo

💣 NULL — тихий саботаж в твоей БД На первый взгляд, NULL — просто отсутствие значения. Но на практике это частый источник багов, неверных аналитик и проблем в бизнес-логике. 📉 Антипаттерн: беспечное обращение с NULL Примеры: SELECT * FROM users WHERE age > 18; -- Пользователи с age = NULL не попадут Ты думаешь, что отбираешь всех взрослых, но age = NULL тут "выпадает", ведь NULL > 18 → UNKNOWN. WHERE col1 =…

👍3❤1

19 Oct 2026, 06:54 UTC≈1,000 views6 reactionsread 12 November 2026

⚡️ Индексы в базах данных: как заставить запросы летать Представь, что тебе нужно найти нужную главу в техническом справочнике на 1000 страниц. Без оглавления придется листать всё подряд (в базах данных это называется Full Table Scan - страшный сон любого админа). Индекс - это и есть то самое оглавление. Как это работает под капотом? Чаще всего индексы строятся на основе B-деревьев (B-Tree) или хэш-таблиц. Суть в т…

👍3🔥2❤1

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

Names

Channels on the register whose handles appear in this channel's posts.

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.

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.

Библиотека программиста (книги для разработчиков)
@programmist_of · 20,570
Telegram ranks this channel #5 of 63 here — alongside 62 others — read 5 October 2026
Книги для Системного Администратора
@i_odmin_book · 18,778
Telegram ranks this channel #22 of 83 here — alongside 82 others — read 5 October 2026
Базы данных | Access, SQL, Big Data
@databases_secrets · 30,000
Telegram ranks this channel #33 of 82 here — alongside 81 others — read 7 September 2026
Системный администратор
@i_odmin · 26,713
Telegram ranks this channel #39 of 89 here — alongside 88 others — read 12 September 2026
КЛУБ | ENGLISH GALAXY | АНГЛИЙСКИЙ ЯЗЫК ПО ПЛЕЙЛИСТАМ
@englishgalaxy_school · 79,402
Telegram ranks this channel #80 of 83 here — alongside 82 others — read 19 August 2026

This channel appears in 5 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 11 November 2026 — this entry's latest reading, not the date you are reading this.

“Базы данных (Data Base)” (@database_info), 8,021 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/database_info.

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.