一名数据库爱好者的专栏

以前一直有些迷惑，一直以为v$open_cursor里查询出来就是当前open的cursor，google收藏了一些讨论得比较深入的帖，比如说这里： 。[@more@]今天看到Natalka Roshak写的一篇关于open_cursors及session_cached_cursors的文章，顿时一目了然，参见：，摘录部分精彩内容如下：SESSION_CACHED_CURSORS sets the number of cached closed cursors each session can have

<<PostgreSQL的WAL(1)–Buffer Cache>><<PostgreSQL的WAL(2)–Write-Ahead Log>><<PostgreSQL的WAL(3)–Checkpoint>><<PostgreSQL的WAL(4)–WAL创建和调优>>

SELECT * FROM tmp_t0;WARNING: page verification failed, calculated checksum 23222 but expected 50884ERROR: invalid page in block 0 of relation base/16386/24890但是，如果无法从备份还原数据，我们该怎么办？ 当然，ignore_checksum_failure参数使您能够尝试读取表，但有可能损坏数据。SET ignore_checksum_

http://blog.chinaunix.net/uid-20726500-id-5766987.html

In an Oracle 12c container database, the client must specify a service name in order to connect to the PDB. Many Database clients with earlier releases of Oracle Database might have hard-coded connect descriptors to use SID to connect to the database. Now

In the previous articles we discussed PostgreSQL indexing engine and the interface of access methods, as well as B-trees, GiST, SP-GiST, GIN, RUM, and BRIN. But we still need to look at Bloom indexes.BloomGeneral conceptA classical Bloom filter is a dat

In the previous articles we discussed PostgreSQL indexing engine, the interface of access methods, and the following methods: B-trees, GiST, SP-GiST, GIN, and RUM. The topic of this article is BRIN indexes.BRINGeneral conceptUnlike indexes with which we

We have already discussed PostgreSQL indexing engine, the interface of access methods, and main access methods, such as: hash indexes, B-trees, GiST, SP-GiST, and GIN. In this article, we will watch how gin turns into rum.RUMAlthough the authors claim th

We have already got acquainted with PostgreSQL indexing engine and the interface of access methods and discussed hash indexes, B-trees, as well as GiST and SP-GiST indexes. And this article will feature GIN index.GIN“Gin?.. Gin is, it seems, such an Amer

We’ve already discussed PostgreSQL indexing engine, the interface of access methods, and three methods: hash index, B-tree, and GiST. In this article, we will describe SP-GiST.SP-GiSTFirst, a few words about this name. The “GiST” part alludes to some sim

In the previous articles, we discussed PostgreSQL indexing engine, the interface of access methods, and two access methods: hash index and B-tree. In this article, we will describe GiST indexes.GiSTGiST is an abbreviation of “generalized search tree”. Th

We’ve already discussed PostgreSQL indexing engine and interface of access methods, as well as hash index, one of access methods. We will now consider B-tree, the most traditional and widely used index. This article is large, so be patient.BtreeStructure

The first article described PostgreSQL indexing engine, the second one dealt with the interface of access methods, and now we are ready to discuss specific types of indexes. Let’s start with hash index.HashStructureGeneral theoryPlenty of modern progra

InterfaceIn the first article, we’ve mentioned that an access method must provide information about itself. Let’s look into the structure of the access method interface.PropertiesAll properties of access methods are stored in the “pg_am” table (“am” sta

IntroductionThis series of articles is largely concerned with indexes in PostgreSQL.Any subject can be considered from different perspectives. We will discuss matters that should interest an application developer who uses DBMS: what indexes are available

作者 | Jose Finotto译者 | 马可薇策划 | 万佳2020 年 5 月，我们与 OnGres 合作，对 GitLab 上的 Postgres 集群进行版本大更新，从 9.6 版本升级到 11 版本。升级全部在维护窗口内运行，没有丝毫差错；更新中所有涉及的内容、计划、测试，以及全流程自动化，全部进行拆包，只为实现一次近乎完美的 PostgreSQL 升级。本次版本更新，我们面临的 最大难题在于如何利用一个规划完善的 pg_upgrade，方便且高效地对整体项目进行重要版本升级。为此，我们

数据库“断页”是个很有意思的话题，目前任何数据库应该都绕不过去。我们知道数据库的块大小一般是8k、16k、32k，而操作系统块大小是4k，那么在数据库刷内存中的数据页到磁盘上的时候，就有可能中途遭遇类似操作系统异常断电而导致数据页部分写的情况，进而造成数据块损坏，数据块损坏对于某些数据库是致命的，可能导致数据库无法启动。既然对于断页问题数据库都可能遇到，那么再来看看主流数据库是如何避免发生断页的。先看看mysql，innodb的page size一般是16k，innodb的数据行发生变更时，将buffer

任何一个数据库最主要功能之一是可扩展。如果不删除彼此，则尽可能较少锁竞争从而达到这个目的。由于read、write、update、delete是数据库中最主要且频繁进行的操作，所以并发执行这些操作时不被阻塞则显得非常重要。为了达到这种目的，大部分数据库使用多版本并发控制（Multi-Version Concurrency Control）这种并发模型。这种模型能够将竞争减少到最低限度。MVCC是什么Multi Version Concurrency Control ( MVCC)是这样的一种算法：通过.

如同没有十全十美的人，一个产品哪里有十全十美的，不怕有缺点，就怕没认知。那么如果从“处女座” 挑剔的角度来看POSTGRESQL 那么到底怎么能从“鸡蛋里面”挑挑骨头，让PG 下不来台。攻击—问题1 ：多版本控制方式垃圾众所周知，postgresql 的MVCC多版本控制以及事务回滚段，并非用 ORACLE ，MYSQL的集中式的方式来进行解决，而是通过在每个表中的每行通过保存多个行版本来解决，导致一个表会存储很多行版本的数据，最终导致表膨胀。同时一个update 相当于 insert ,delete操

Autonomous Health Framework (AHF) - Including TFA and ORAchk/EXAchk (文档 ID 2550798.1)# su - oracle$ cd /tmp$ rz$ ls -l AHF*-rw-r--r-- 1 oracle oinstall 417185977 Feb 7 18:00 AHF-LINUX_v21.4.1.zip$ unzip AHF-LINUX_v21.4.1.zipArchive: ./AHF-LINUX