Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commita1e6023

Browse files
authored
Update logo and diagram in README (#163)
1 parent63140da commita1e6023

File tree

5 files changed

+67
-2
lines changed

5 files changed

+67
-2
lines changed

‎README.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
[![PGXN version](https://badge.fury.io/pg/rum.svg)](https://badge.fury.io/pg/rum)
33
[![GitHub license](https://img.shields.io/badge/license-PostgreSQL-blue.svg)](https://raw.githubusercontent.com/postgrespro/rum/master/LICENSE)
44

5-
[![Postgres Professional](img/PGpro-logo.png)](https://postgrespro.com/)
5+
[![Postgres Professional](img/PGpro-logo.svg)](https://postgrespro.com/)
66

77
#RUM - RUM access method
88

@@ -26,7 +26,7 @@ in the index with lexemes. So it is necessary to perform an additional heap scan
2626
For example, positional information of lexemes or timestamps. You can get an
2727
idea of`RUM` with the following diagram:
2828

29-
![How RUM stores additional information](img/gin_rum.png)
29+
[![How RUM stores additional information](img/gin_rum.svg)](https://postgrespro.ru/docs/enterprise/current/rum?lang=en)
3030

3131
A drawback of`RUM` is that it has slower build and insert times than`GIN`.
3232
This is because we need to store additional information besides keys and because

‎img/PGpro-logo.png‎

-20.7 KB
Binary file not shown.

‎img/PGpro-logo.svg‎

Lines changed: 17 additions & 0 deletions
Loading

‎img/gin_rum.png‎

-18.7 KB
Binary file not shown.

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp