PostgreSQL源码分析——备份恢复

在上一篇PostgreSQL源码分析——基础备份中，我们分析了PG中基础备份的过程以及源码，备份与恢复是不分离的，这里我们继续分析一下，从基础备份中进行恢复的源码。

备份过程

执行备份：

postgres=# select pg_start_backup('bak3');pg_start_backup 
-----------------0/6000060
(1 row)postgres=# insert into t1 values(5);
INSERT 0 1
postgres=# select pg_stop_backup();
NOTICE:  WAL archiving is not enabled; you must ensure that all required WAL segments are copied through other means to complete the backuppg_stop_backup 
----------------0/60002D8
(1 row)

查看日志：

postgres@slpc:~/pgsql/pgdata/pg_wal$ pg_waldump -p ../pg_wal 000000010000000000000006
rmgr: Standby     len (rec/tot):     50/    50, tx:          0, lsn: 0/06000028, prev 0/05000110, desc: RUNNING_XACTS nextXid 738 latestCompletedXid 737 oldestRunningXid 738
rmgr: Standby     len (rec/tot):     50/    50, tx:          0, lsn: 0/06000060, prev 0/06000028, desc: RUNNING_XACTS nextXid 738 latestCompletedXid 737 oldestRunningXid 738
rmgr: XLOG        len (rec/tot):    114/   114, tx:          0, lsn: 0/06000098, prev 0/06000060, desc: CHECKPOINT_ONLINE redo 0/6000060; tli 1; prev tli 1; fpw true; xid 0:738; oid 16387; multi 1; offset 0; oldest xid 726 in DB 1; oldest multi 1 in DB 1; oldest/newest commit timestamp xid: 0/0; oldest running xid 738; online
rmgr: Standby     len (rec/tot):     50/    50, tx:          0, lsn: 0/06000110, prev 0/06000098, desc: RUNNING_XACTS nextXid 738 latestCompletedXid 737 oldestRunningXid 738
rmgr: Heap        len (rec/tot):     54/   258, tx:        738, lsn: 0/06000148, prev 0/06000110, desc: INSERT off 5 flags 0x00, blkref #0: rel 1663/13010/16384 blk 0 FPW
rmgr: Transaction len (rec/tot):     34/    34, tx:        738, lsn: 0/06000250, prev 0/06000148, desc: COMMIT 2023-09-18 14:40:06.694650 CST
rmgr: Standby     len (rec/tot):     50/    50, tx:          0, lsn: 0/06000278, prev 0/06000250, desc: RUNNING_XACTS nextXid 739 latestCompletedXid 738 oldestRunningXid 739
rmgr: XLOG        len (rec/tot):     34/    34, tx:          0, lsn: 0/060002B0, prev 0/06000278, desc: BACKUP_END 0/6000060
rmgr: XLOG        len (rec/tot):     24/    24, tx:          0, lsn: 0/060002D8, prev 0/060002B0, desc: SWITCH

查看backup_label文件：

postgres@slpc:~/pgsql/pgbak2$ cat backup_label 
START WAL LOCATION: 0/6000060 (file 000000010000000000000006)
CHECKPOINT LOCATION: 0/6000098
BACKUP METHOD: pg_start_backup
BACKUP FROM: primary
START TIME: 2023-09-18 14:39:50 CST
LABEL: bak3
START TIMELINE: 1
恢复源码分析

启动备份数据库，检测到有backup_label文件时，则认为是从一个备份文件中进行恢复，读取backup_label中的检查点信息，而不是从pg_control中读取。

main(int argc, char *argv[])
--> PostmasterMain(argc, argv);--> LocalProcessControlFile(false);		// 读pg_control文件--> StartupPID = StartupDataBase();		// 启动startup子进程--> StartupProcessMain();--> StartupXLOG();--> ValidateXLOGDirectoryStructure();   // Verify that pg_wal and pg_wal/archive_status exist.--> readRecoverySignalFile();		// Check for signal files, and if so set up state for offline recovery--> validateRecoveryParameters();--> XLogReaderAllocate    // Allocate and initialize a new XLogReader.// 是否存在backup_label文件，如果存在的话，则认为是从一个备份文件进行恢复--> read_backup_label(&checkPointLoc, &backupEndRequired, &backupFromStandby)--> record = ReadCheckpointRecord(xlogreader, checkPointLoc, 0, true); //回放的起点为backup_label中的检查点--> XLogBeginRead(xlogreader, RecPtr);   // Begin reading WAL at 'RecPtr'.--> record = ReadRecord(xlogreader, LOG, true);for (;;){record = XLogReadRecord(xlogreader, &errormsg);		// Attempt to read an XLOG record.}--> StartupCLOG();/* REDO */if (InRecovery){UpdateControlFile();CheckRecoveryConsistency();if (checkPoint.redo < RecPtr){/* back up to find the record */XLogBeginRead(xlogreader, checkPoint.redo);record = ReadRecord(xlogreader, PANIC, false);} else {/* just have to read next record after CheckPoint */record = ReadRecord(xlogreader, LOG, false);}if (record != NULL){/* main redo apply loop */do  // 回放日志{	// 判断否已达到指定恢复位置，PITR用if (recoveryStopsBefore(xlogreader)){reachedRecoveryTarget = true;break;}/* Now apply the WAL record itself */RmgrTable[record->xl_rmid].rm_redo(xlogreader);}}}

核心函数StartupXLOG源码分析：

void StartupXLOG(void)
{// .../* Set up XLOG reader facility */MemSet(&private, 0, sizeof(XLogPageReadPrivate));xlogreader = XLogReaderAllocate(wal_segment_size, NULL, XL_ROUTINE(.page_read = &XLogPageRead, .segment_open = NULL, .segment_close = wal_segment_close), &private);// 读backup_label文件if (read_backup_label(&checkPointLoc, &backupEndRequired, &backupFromStandby)){/* Archive recovery was requested, and thanks to the backup label* file, we know how far we need to replay to reach consistency. Enter* archive recovery directly. */InArchiveRecovery = true;/* When a backup_label file is present, we want to roll forward from* the checkpoint it identifies, rather than using pg_control. */record = ReadCheckpointRecord(xlogreader, checkPointLoc, 0, true);if (record != NULL){memcpy(&checkPoint, XLogRecGetData(xlogreader), sizeof(CheckPoint));/* Make sure that REDO location exists. This may not be the case* if there was a crash during an online backup, which left a* backup_label around that references a WAL segment that's already been archived. */if (checkPoint.redo < checkPointLoc){XLogBeginRead(xlogreader, checkPoint.redo);if (!ReadRecord(xlogreader, LOG, false))ereport(FATAL,(errmsg("could not find redo location referenced by checkpoint record"), errhint("If you are restoring from a backup, touch \"%s/recovery.signal\" and add required recovery options.\n" "If you are not restoring from a backup, try removing the file \"%s/backup_label\".\n" "Be careful: removing \"%s/backup_label\" will result in a corrupt cluster if restoring from a backup.", DataDir, DataDir, DataDir)));}}else{ereport(FATAL,(errmsg("could not locate required checkpoint record"),errhint("If you are restoring from a backup, touch \"%s/recovery.signal\" and add required recovery options.\n""If you are not restoring from a backup, try removing the file \"%s/backup_label\".\n""Be careful: removing \"%s/backup_label\" will result in a corrupt cluster if restoring from a backup.", DataDir, DataDir, DataDir)));wasShutdown = false;	/* keep compiler quiet */}/* set flag to delete it later */haveBackupLabel = true;}else  // 如果没有backup_label文件，则读pg_control文件，在备机恢复的场景中，如果丢失了backup_label文件，而读取了pg_control文件中的检查点，则会因为回放位置不对，无法达成数据一致，恢复失败。{/* Get the last valid checkpoint record. */checkPointLoc = ControlFile->checkPoint;RedoStartLSN = ControlFile->checkPointCopy.redo;record = ReadCheckpointRecord(xlogreader, checkPointLoc, 1, true);if (record != NULL){ereport(DEBUG1,(errmsg_internal("checkpoint record is at %X/%X", LSN_FORMAT_ARGS(checkPointLoc))));}else{/** We used to attempt to go back to a secondary checkpoint record* here, but only when not in standby mode. We now just fail if we* can't read the last checkpoint because this allows us to* simplify processing around checkpoints.*/ereport(PANIC,(errmsg("could not locate a valid checkpoint record")));}memcpy(&checkPoint, XLogRecGetData(xlogreader), sizeof(CheckPoint));}/* REDO */if (InRecovery){/** Set backupStartPoint if we're starting recovery from a base backup.** Also set backupEndPoint and use minRecoveryPoint as the backup end* location if we're starting recovery from a base backup which was* taken from a standby. In this case, the database system status in* pg_control must indicate that the database was already in recovery.* Usually that will be DB_IN_ARCHIVE_RECOVERY but also can be* DB_SHUTDOWNED_IN_RECOVERY if recovery previously was interrupted* before reaching this point; e.g. because restore_command or primary_conninfo were faulty.** Any other state indicates that the backup somehow became corrupted and we can't sensibly continue with recovery.*/if (haveBackupLabel){ControlFile->backupStartPoint = checkPoint.redo;		// 从基础备份中恢复ControlFile->backupEndRequired = backupEndRequired;if (backupFromStandby){if (dbstate_at_startup != DB_IN_ARCHIVE_RECOVERY &&dbstate_at_startup != DB_SHUTDOWNED_IN_RECOVERY)ereport(FATAL,(errmsg("backup_label contains data inconsistent with control file"),errhint("This means that the backup is corrupted and you will ""have to use another backup for recovery.")));ControlFile->backupEndPoint = ControlFile->minRecoveryPoint;}}UpdateControlFile();	// 更新pg_control，主要是将Backup start location写入/** We're in recovery, so unlogged relations may be trashed and must be* reset.  This should be done BEFORE allowing Hot Standby* connections, so that read-only backends don't try to read whatever* garbage is left over from before.*/ResetUnloggedRelations(UNLOGGED_RELATION_CLEANUP);/* Initialize resource managers */for (rmid = 0; rmid <= RM_MAX_ID; rmid++){if (RmgrTable[rmid].rm_startup != NULL)RmgrTable[rmid].rm_startup();}CheckRecoveryConsistency();		// Checks if recovery has reached a consistent state./** Find the first record that logically follows the checkpoint --- it* might physically precede it, though. */if (checkPoint.redo < RecPtr){/* back up to find the record */XLogBeginRead(xlogreader, checkPoint.redo);record = ReadRecord(xlogreader, PANIC, false);}else{/* just have to read next record after CheckPoint */record = ReadRecord(xlogreader, LOG, false);}if (record != NULL){// 在这里进行实质的日志回放/* main redo apply loop */do{bool		switchedTLI = false;// 用于PITR，判断是否已经回放到了指定的Target/* Have we reached our recovery target? */if (recoveryStopsBefore(xlogreader)){reachedRecoveryTarget = true;break;}/* Now apply the WAL record itself */RmgrTable[record->xl_rmid].rm_redo(xlogreader);		// 调用standby_redo,xlog_redo,heap_redo，xact_redo等，进行回放，/* Allow read-only connections if we're consistent now */CheckRecoveryConsistency();/* Exit loop if we reached inclusive recovery target */if (recoveryStopsAfter(xlogreader)){reachedRecoveryTarget = true;break;}/* Else, try to fetch the next WAL record */record = ReadRecord(xlogreader, LOG, false);	} while (record != NULL);  // 直到结束}}/** Determine where to start writing WAL next.** When recovery ended in an incomplete record, write a WAL record about* that and continue after it.  In all other cases, re-fetch the last* valid or last applied record, so we can identify the exact endpoint of* what we consider the valid portion of WAL.*/XLogBeginRead(xlogreader, LastRec);record = ReadRecord(xlogreader, PANIC, false);EndOfLog = EndRecPtr;// ...}

一直回放到XLOG_BACKUP_END，

/** XLOG resource manager's routines** Definitions of info values are in include/catalog/pg_control.h, though* not all record types are related to control file updates.*/
void xlog_redo(XLogReaderState *record)
{uint8		info = XLogRecGetInfo(record) & ~XLR_INFO_MASK;XLogRecPtr	lsn = record->EndRecPtr;if (info == XLOG_NEXTOID){// ...}else if (info == XLOG_CHECKPOINT_SHUTDOWN){CheckPoint	checkPoint;memcpy(&checkPoint, XLogRecGetData(record), sizeof(CheckPoint));// ...RecoveryRestartPoint(&checkPoint);}else if (info == XLOG_CHECKPOINT_ONLINE){CheckPoint	checkPoint;memcpy(&checkPoint, XLogRecGetData(record), sizeof(CheckPoint));// ...RecoveryRestartPoint(&checkPoint);}else if (info == XLOG_OVERWRITE_CONTRECORD){xl_overwrite_contrecord xlrec;memcpy(&xlrec, XLogRecGetData(record), sizeof(xl_overwrite_contrecord));VerifyOverwriteContrecord(&xlrec, record);}else if (info == XLOG_END_OF_RECOVERY){xl_end_of_recovery xlrec;memcpy(&xlrec, XLogRecGetData(record), sizeof(xl_end_of_recovery));/** For Hot Standby, we could treat this like a Shutdown Checkpoint,* but this case is rarer and harder to test, so the benefit doesn't* outweigh the potential extra cost of maintenance.*//** We should've already switched to the new TLI before replaying this* record.*/if (xlrec.ThisTimeLineID != ThisTimeLineID)ereport(PANIC,(errmsg("unexpected timeline ID %u (should be %u) in checkpoint record",xlrec.ThisTimeLineID, ThisTimeLineID)));}else if (info == XLOG_NOOP){/* nothing to do here */}else if (info == XLOG_SWITCH){/* nothing to do here */}else if (info == XLOG_RESTORE_POINT){/* nothing to do here */}else if (info == XLOG_FPI || info == XLOG_FPI_FOR_HINT){/** Full-page image (FPI) records contain nothing else but a backup* block (or multiple backup blocks). Every block reference must* include a full-page image - otherwise there would be no point in* this record.** No recovery conflicts are generated by these generic records - if a* resource manager needs to generate conflicts, it has to define a* separate WAL record type and redo routine.** XLOG_FPI_FOR_HINT records are generated when a page needs to be* WAL- logged because of a hint bit update. They are only generated* when checksums are enabled. There is no difference in handling* XLOG_FPI and XLOG_FPI_FOR_HINT records, they use a different info* code just to distinguish them for statistics purposes.*/for (uint8 block_id = 0; block_id <= record->max_block_id; block_id++){Buffer		buffer;if (XLogReadBufferForRedo(record, block_id, &buffer) != BLK_RESTORED)elog(ERROR, "unexpected XLogReadBufferForRedo result when restoring backup block");UnlockReleaseBuffer(buffer);}}else if (info == XLOG_BACKUP_END)	// 回放到这里，结束备份恢复过程{XLogRecPtr	startpoint;memcpy(&startpoint, XLogRecGetData(record), sizeof(startpoint));if (ControlFile->backupStartPoint == startpoint){/** We have reached the end of base backup, the point where* pg_stop_backup() was done. The data on disk is now consistent.* Reset backupStartPoint, and update minRecoveryPoint to make* sure we don't allow starting up at an earlier point even if* recovery is stopped and restarted soon after this.*/elog(DEBUG1, "end of backup reached");LWLockAcquire(ControlFileLock, LW_EXCLUSIVE);if (ControlFile->minRecoveryPoint < lsn){ControlFile->minRecoveryPoint = lsn;ControlFile->minRecoveryPointTLI = ThisTimeLineID;}ControlFile->backupStartPoint = InvalidXLogRecPtr;ControlFile->backupEndRequired = false;UpdateControlFile();LWLockRelease(ControlFileLock);}}else if (info == XLOG_PARAMETER_CHANGE){// ...}else if (info == XLOG_FPW_CHANGE){// ...}
}

本文来自互联网用户投稿，该文观点仅代表作者本人，不代表本站立场。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如若转载，请注明出处：http://www.mzph.cn/web/30681.shtml

如若内容造成侵权/违法违规/事实不符，请联系多彩编程网进行投诉反馈email:809451989@qq.com，一经查实，立即删除！

相关文章

《模拟联合国2.9—团队协作》

《模拟联合国2.9—团队协作》

感谢上海财经大学持续的邀请&#xff0c;今天在阶梯教室举办的《模拟联合国2.0—团队协作》沙盘课程圆满结束。尽管场地的限制带来了一定的挑战&#xff0c;但得益于系统思考中“结构影响行为”的原则&#xff0c;我得以在不同场景中巧妙设计课程结构&#xff0c;极大地促进了大…
阅读更多...
云顶森林的新守护者：大数据平台的智慧力量

云顶森林的新守护者：大数据平台的智慧力量

在遥远的云顶之上&#xff0c;有一片生机盎然的森林&#xff0c;它不仅是动植物的家园&#xff0c;更是自然与人类和谐共生的典范。然而&#xff0c;如何在这片广袤的森林中实施高效、科学的管理&#xff0c;一直是一个摆在管理者面前的难题。幸运的是&#xff0c;随着科技的飞…
阅读更多...
jQuery 样式操作

jQuery 样式操作

3.tab栏切换案例 实现效果&#xff1a; 案例分析&#xff1a; 核心代码&#xff1a; html结构&#xff1a; 4.jQuery类操作与className区别 1.操作css方法 jQuery可以使用Css方法来修改简单元素样式;可以操作类,修改多个样式。 参数只写属性名&#xff0c;则是返回属性值…
阅读更多...
如何在购买的服务器上进行开发工作？

如何在购买的服务器上进行开发工作？

1. 连接服务器 首先需要通过SSH&#xff08;Secure Shell&#xff09;协议连接到服务器。这通常涉及到以下步骤&#xff1a; 使用SSH客户端软件&#xff08;如PuTTY在Windows上&#xff0c;或使用终端在Linux/MacOS上&#xff09;。输入服务器的IP地址或域名输入密码或使用密…
阅读更多...
WordPress插件数据库批量替换内容工具插件

WordPress插件数据库批量替换内容工具插件

1、安装插件后&#xff0c;我们就可以在后台菜单看到工具操作界面 2、目前支持网站内容、标题、评论指定字符的快速替换 3、可以快速解决以往我们需要从MYSQL数据库命令替换的烦恼
阅读更多...
DNF安卓分离仅是开始：游戏厂商积极布局自有渠道，市场变革在即

DNF安卓分离仅是开始：游戏厂商积极布局自有渠道，市场变革在即

毫无征兆&#xff0c;DNF手游今天突然宣布从各大安卓平台下架。 《地下城与勇士:起源》运营团队于6月19日发布声明&#xff0c;指出因合约到期&#xff0c;游戏将不再上架部分安卓平台的应用商店。然而&#xff0c;这一事件并非完全无迹可循。 早在2021年初&#xff0c;华为游…
阅读更多...
51单片机STC89C52RC——2.3 两个独立按键模拟控制LED流水灯方向

51单片机STC89C52RC——2.3 两个独立按键模拟控制LED流水灯方向

目的 按下K1键LED流水向左移动 按下K2键LED流水向右移动 一&#xff0c;STC单片机模块 二&#xff0c;独立按键 2.1 独立按键位置 2.2 独立按键电路图 这里要注意一个设计的bug P3_1 引脚对应是K1 P3_0 引脚对应是K2 要实现按一下点亮、再按一下熄灭&#xff0c;我们就需…
阅读更多...
1688商品详情API：一键解锁海量批发数据

1688商品详情API：一键解锁海量批发数据

引言 1688作为阿里巴巴旗下的B2B交易平台&#xff0c;拥有庞大的商品数据库和丰富的供应商资源。对于想要获取商品详细信息的开发者和企业而言&#xff0c;1688提供的API接口是获取一手数据的关键途径。本文将详细介绍如何使用1688商品详情API&#xff0c;包括注册、获取API密…
阅读更多...
磁盘未格式化深度解析与应对策略

磁盘未格式化深度解析与应对策略

一、认识磁盘未格式化现象 在计算机世界中&#xff0c;磁盘未格式化是一个常见的故障现象。当系统提示磁盘未格式化时&#xff0c;意味着该磁盘或分区上的文件系统结构已损坏或丢失&#xff0c;导致计算机无法正确读取其中的数据。这种情况下&#xff0c;用户通常无法直接访问…
阅读更多...
【Liunx】基础开发工具的使用介绍-- yum / vim / gcc / gdb / make

【Liunx】基础开发工具的使用介绍-- yum / vim / gcc / gdb / make

前言 本章将介绍Linux环境基础开发工具的安装及使用&#xff0c;在Linux下安装软件&#xff0c;编写代码&#xff0c;调试代码等操作。 目录 1. yum 工具的使用1.1 什么是软件包&#xff1a;1.2 如何下载软件&#xff1a;1.3 配置国内yum源&#xff1a; 2. vim编辑器2.1 vim的安…
阅读更多...
【CT】LeetCode手撕—54. 螺旋矩阵

【CT】LeetCode手撕—54. 螺旋矩阵

目录 题目1- 思路2- 实现⭐54. 螺旋矩阵——题解思路 3- ACM实现 题目 原题连接&#xff1a;92. 反转链表 II 1- 思路 模式识别&#xff1a;螺旋矩阵 ——> 用四个指针来顺时针遍历 2- 实现 ⭐54. 螺旋矩阵——题解思路 class Solution {public List<Integer> spir…
阅读更多...
目标检测——轮胎纹理图像识别技术：从数据到应用全解析

目标检测——轮胎纹理图像识别技术：从数据到应用全解析

引言 亲爱的读者们&#xff0c;您是否在寻找某个特定的数据集&#xff0c;用于研究或项目实践&#xff1f;欢迎您在评论区留言&#xff0c;或者通过公众号私信告诉我&#xff0c;您想要的数据集的类型主题。小编会竭尽全力为您寻找&#xff0c;并在找到后第一时间与您分享。 一…
阅读更多...
哈喽GPT-4o——对GPT-4o 编程的思考与看法

哈喽GPT-4o——对GPT-4o 编程的思考与看法

GPT-4o&#xff08;“o”代表“全能”&#xff09;它可以接受任意组合的文本、音频和图像作为输入&#xff0c;并生成任意组合的文本、音频和图像输出。 &#x1f449; GPT功能&#xff1a; GPT-4o知识问答&#xff1a;支持1000token上下文记忆功能最强代码大模型Code Copilo…
阅读更多...
ctr/cvr预估之FM模型

ctr/cvr预估之FM模型

ctr/cvr预估之FM模型 在数字化时代&#xff0c;广告和推荐系统的质量直接影响着企业的营销成效和用户体验。点击率&#xff08;CTR&#xff09;和转化率&#xff08;CVR&#xff09;预估作为这些系统的核心组件&#xff0c;其准确性至关重要。传统的机器学习方法&#xff0c;如…
阅读更多...
微信公众号绑定开发者后端，报错“系统发生错误，请稍后重试”的坑

微信公众号绑定开发者后端，报错“系统发生错误，请稍后重试”的坑

一、问题描述 在公众号后端填写完基本配置&#xff0c;点击保存&#xff0c;发现提示“系统发生错误&#xff0c;请稍后重试”。联系公众号客服回复&#xff0c;涉及开发内容不给支持-_-|| 二、经多次百度&#xff0c;结合实际尝试&#xff0c;总结解决方案如下&#xff1a;…
阅读更多...
电子竞赛4——李沙育图形演示电路

电子竞赛4——李沙育图形演示电路

一.系统设计 1.1 设计要求 设计制作一个X-Y信号产生与图形显示装置&#xff0c;示意图如图1所示。图中示波器工作在X-Y方式&#xff1b;外加正弦信号的频率为100KHz左右&#xff0c;电压峰峰值为2V。 基本要求: &#xff08;1&#xff09; 设计并制作一组移相分别为45、90、…
阅读更多...
新世纪助力无锡市第二人民医院通过ITSS认证

新世纪助力无锡市第二人民医院通过ITSS认证

通过江苏新世纪信息科技有限公司的咨询辅导&#xff0c;无锡市第二人民医院通过合规性审查、复核、评定审核环节&#xff0c;顺利完成ITSS通用要求的认证。近日&#xff0c;评定结果在“ITSS中国电子工业标准化技术协会信息技术服务分会”网站&#xff08;https://www.itss.cn&…
阅读更多...
redis的序列化问题

redis的序列化问题

报错 io.netty.handler.codec.DecoderException: com.fasterxml.jackson.databind.exc.InvalidDefinitionException: Cannot construct instance of org.springframework.http.ReadOnlyHttpHeaders (no Creators, like default constructor, exist): no default constructor f…
阅读更多...
华为数通——单臂路由

华为数通——单臂路由

单臂路由&#xff1a;指在三层设备路由器的一个接口上通过配置子接口&#xff08;或“逻辑接口”&#xff0c;并不存在真正物理接口&#xff09;的方式&#xff0c;实现原来相互隔离的不同VLAN&#xff08;虚拟局域网&#xff09;之间的互联互通。但是仅仅允许单播通信。 单臂路…
阅读更多...
张一鸣的产品哲学：与巨头共舞，低调中寻求突破

张一鸣的产品哲学：与巨头共舞，低调中寻求突破

一、引言 在当今互联网竞争激烈的格局下&#xff0c;与巨头企业打交道是每个新兴科技企业都需面对的挑战。字节跳动创始人张一鸣在多次访谈中分享了他与巨头企业打交道的经验&#xff1a;保持低调、补齐技术、产品和市场各方面的能力。本文将探讨这一策略背后的产品哲学&#…
阅读更多...
最新文章

Copyright @ 2022~2023