Hi! All Ok! Very-very thanks!
On Fri, Jul 24, 2026 at 7:35 AM Dianjin Wang <[email protected]> wrote: > Hi Leonid, > > After coordination with the organization committee, your session has > been rescheduled. Welcome to take a look: > https://asia.communityovercode.org/sessions/observability-1195519.html. > > > Best, > Dianjin Wang > > > On Fri, Jul 24, 2026 at 12:04 AM Leonid Borchuk <[email protected]> > wrote: > > > > Hi! > > > > Are there any possibilities to change the schedule? I have a speech at > > 2026-08-09 13:30 GMT+8 (in track observability), but my departure flight > is > > at 14:25. There is no chance to do everything in time ) > > > > On Fri, Jul 17, 2026 at 3:46 PM Dianjin Wang <[email protected]> > wrote: > > > > > Hi all, > > > > > > Congratulations again to everyone whose talks have been accepted for > > > Community Over Code Asia 2026! > > > > > > To help the conference organizers finalize the speaker list and > > > schedule, please make sure to confirm your participation by clicking > > > the “Confirm Participation” button in the original acceptance > > > notification email from Sessionize. > > > > > > If you have already confirmed, no further action is needed. > > > > > > Thanks again for your contribution to the Apache Cloudberry community. > > > Looking forward to seeing your great sessions at Community Over Code > > > Asia 2026! > > > > > > Best, > > > Dianjin Wang > > > > > > On Mon, Jul 13, 2026 at 12:41 PM Dianjin Wang <[email protected]> > > > wrote: > > > > > > > > Hi all, > > > > > > > > The draft schedule for COC Asia 2026 is out! There will be seven > > > > sessions on Cloudberry at the upcoming conference. Congratulations to > > > > all of you, and thanks, everyone! We also plan to hold an in-person > > > > gathering in Beijing during the conference; the topics will focus on > > > > Cloudberry's incubation, graduation, and community. If you have any > > > > topics to discuss, please leave your comments. > > > > > > > > ~~~~ > > > > > > > > #Data Lake & Data Warehouse > > > > What's new in Apache Cloudberry (Incubating) 2.1 and 3.0, Max Yang > > > > https://asia.communityovercode.org/sessions/datalake-1213358.html > > > > > > > > #Data Storage & Computing > > > > When the Optimizer Lies: Debugging Cross-Slice Execution in Apache > > > > Cloudberry, Alena Rybakina > > > > https://asia.communityovercode.org/sessions/datastorage-1213149.html > > > > > > > > #Incubator > > > > Beyond Incubation: Building a Sustainable Apache Community with > > > > Cloudberry, Dianjin Wang > > > > https://asia.communityovercode.org/sessions/incubator-1210256.html > > > > > > > > #Incubator > > > > Build Once, Run on Any Linux: SynxDB CE for Apache Cloudberry > > > > (Incubating), Shine Zhang & Ed Espino > > > > https://asia.communityovercode.org/sessions/incubator-1212002.html > > > > > > > > #Observability > > > > Apache Cloudberry: gathering statistics for queries executed by > > > > multiple PostgreSQL instances. Leonid Borchuk > > > > > https://asia.communityovercode.org/sessions/observability-1195519.html > > > > > > > > #OLAP & Data Analysis > > > > Deep Dive into Parallel Query Execution Solutions for Apache > > > > Cloudberry, Rose Duan > > > > https://asia.communityovercode.org/sessions/olap-1210336.html > > > > > > > > #OLAP & Data Analysis > > > > We tried DPDK for network but failed. Why and what we have learned > > > > from this? Leonid Borchuk > > > > https://asia.communityovercode.org/sessions/olap-1195516.html > > > > > > > > > > > > Best, > > > > Dianjin Wang > > > > > > > > On Thu, Apr 16, 2026 at 11:43 PM Leonid Borchuk < > [email protected]> > > > wrote: > > > > > > > > > > Hi! > > > > > > > > > > Thank you, fixed - now the topic is "Apache Cloudberry: gathering > > > > > statistics for queries executed by multiple PostgreSQL instances." > ) > > > > > > > > > > Also thank you for the link to the assistance service, I'll keep > him > > > in mind > > > > > . > > > > > > > > > > On Thu, Apr 16, 2026 at 9:57 AM Dianjin Wang < > [email protected]> > > > wrote: > > > > > > > > > > > Hi Leonid, > > > > > > > > > > > > I took a look at your second proposal, “Outside of > > > pg_stat_statements: > > > > > > if your query is executed by multiple PostgreSQL instances” — > it’s a > > > > > > very practical and interesting topic. > > > > > > > > > > > > One small suggestion: since Community Over Code is strongly > > > > > > Apache-focused, do you think it might be possible to create some > > > > > > connection to Apache projects (e.g., Cloudberry or the broader > Apache > > > > > > ecosystem)? Even a light touch there could help strengthen its > fit > > > and > > > > > > improve acceptance chances. Just a thought! > > > > > > > > > > > > Also, in case it’s helpful — the event provides Travel > Assistance: > > > > > > https://tac.apache.org/events/current.html. If other community > > > members > > > > > > want to get travel assistance, can apply for it. > > > > > > > > > > > > I'm also preparing a talk and will share it soon. > > > > > > > > > > > > Best, > > > > > > Dianjin Wang > > > > > > > > > > > > On Mon, Mar 30, 2026 at 7:07 PM Leonid Borchuk < > [email protected] > > > > > > > > > > wrote: > > > > > > > > > > > > > > Hi! > > > > > > > > > > > > > > Thank you, I opened a proposal for 2 sessions: > > > > > > > > > > > > > > We tried DPDK for network but failed. Why and what we have > learned > > > from > > > > > > > this? > > > > > > > Description > > > > > > > > > > > > > > The CPU frequency is practically not growing, but everything > else: > > > > > > > network/ssd/ data volumes are growing exponentially. This > poses new > > > > > > > challenges for the databases: reduce CPU costs for working > with the > > > > > > > infrastructure. The bottleneck of MPP systems is the network. > What > > > > > > happens > > > > > > > if the network in Greenplum becomes 10 times faster? We > > > accelerated 5 > > > > > > > times. Then we tried DPDK, but realized that we couldn't move > > > forward > > > > > > > without serious core refinement. I would share what happened > to the > > > > > > > database when the network accelerated 5 times. And also why > DPDK > > > didn't > > > > > > > start. > > > > > > > What conclusions have we learned and what are we planning to do > > > next > > > > > > > (spoiler: all new changes will be in Apache Cloudberry). > > > > > > > Session format > > > > > > > > > > > > > > Session > > > > > > > Track > > > > > > > > > > > > > > OLAP & Data Analysis > > > > > > > Level > > > > > > > > > > > > > > Intermediate > > > > > > > Language > > > > > > > > > > > > > > English > > > > > > > > > > > > > > Outside of pg_stat_statements: if your query is executed by > > > multiple > > > > > > > PostgreSQL instances > > > > > > > Description > > > > > > > > > > > > > > Let's say you have several PostgreSQL instances, they all > execute a > > > > > > single > > > > > > > query, and you want to collect general statistics on how many > > > resources > > > > > > > were spent on executing this query. The built-in > pg_stat_statements > > > > > > module > > > > > > > is no longer suitable here, since it works within the same > > > database. I > > > > > > will > > > > > > > present a solution with a similar central idea — collecting > data > > > through > > > > > > > query execution hooks, but instead of storing it in PostgreSQL > > > shared > > > > > > > memory, we send raw data to an external agent process. This > > > process is > > > > > > > responsible for aggregating metrics, providing a unified > picture > > > across > > > > > > all > > > > > > > instances, as well as additional functions, such as the forced > > > > > > termination > > > > > > > of problematic sessions, while not limited to PostgreSQL: the > > > solution > > > > > > can > > > > > > > collect data from other system components. I will talk about > > > > > > architecture, > > > > > > > product tasks, and share links to the repositories (Apache 2.0 > > > License) > > > > > > > with the code. > > > > > > > Session format > > > > > > > > > > > > > > Session > > > > > > > Track > > > > > > > > > > > > > > Observability > > > > > > > Level > > > > > > > > > > > > > > Advanced > > > > > > > Language > > > > > > > > > > > > > > English > > > > > > > > > > > > > > On Mon, Mar 23, 2026 at 4:02 AM Dianjin Wang < > > > [email protected]> > > > > > > wrote: > > > > > > > > > > > > > > > Hi all, > > > > > > > > > > > > > > > > I’d like to share that the Call for Proposals (CFP) for > > > Community Over > > > > > > > > Code Asia 2026 is now open: > > > > > > > > https://sessionize.com/community-over-code-asia-2026/ > > > > > > > > > > > > > > > > Community Over Code Asia 2026 will be held in Beijing from > > > August 7 to > > > > > > 9, > > > > > > > > 2026. > > > > > > > > > > > > > > > > I’d like to encourage everyone in the Apache Cloudberry > > > community to > > > > > > > > consider submitting talk proposals. There are multiple tracks > > > that > > > > > > > > could be a good fit for Cloudberry-related topics, including > for > > > > > > > > example: > > > > > > > > > > > > > > > > - Data + AI > > > > > > > > - Data Lake & Data Warehouse > > > > > > > > - Incubator > > > > > > > > - OLAP & Data Analysis > > > > > > > > > > > > > > > > You can also find the full list of tracks here: > > > > > > > > https://asia.communityovercode.org/tracks.html > > > > > > > > > > > > > > > > This is a great opportunity to share our technical progress, > > > community > > > > > > > > journey, user stories, ecosystem work, and ideas around > Apache > > > > > > > > Cloudberry with the broader open source community. > > > > > > > > > > > > > > > > The CFP deadline is 21 April 2026, so now is a good time to > start > > > > > > > > preparing proposals. > > > > > > > > > > > > > > > > If you already have a topic in mind but would like help > refining > > > the > > > > > > > > title, abstract, or track selection, feel free to start a > > > discussion > > > > > > > > on the mailing list. > > > > > > > > > > > > > > > > Best, > > > > > > > > Dianjin Wang > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > > To unsubscribe, e-mail: > [email protected] > > > > > > > > For additional commands, e-mail: > [email protected] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: [email protected] > > > > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
