diff --git a/README.md b/README.md index 684935bf54..a9e0d8ab63 100644 --- a/README.md +++ b/README.md @@ -2,7 +2,7 @@ [![PGXN version](https://badge.fury.io/pg/rum.svg)](https://badge.fury.io/pg/rum) [![GitHub license](https://img.shields.io/badge/license-PostgreSQL-blue.svg)](https://raw.githubusercontent.com/postgrespro/rum/master/LICENSE) -[![Postgres Professional](img/PGpro-logo.png)](https://postgrespro.com/) +[![Postgres Professional](img/PGpro-logo.svg)](https://postgrespro.com/) # RUM - RUM access method @@ -26,7 +26,7 @@ in the index with lexemes. So it is necessary to perform an additional heap scan For example, positional information of lexemes or timestamps. You can get an idea of `RUM` with the following diagram: -![How RUM stores additional information](img/gin_rum.png) +[![How RUM stores additional information](img/gin_rum.svg)](https://postgrespro.ru/docs/enterprise/current/rum?lang=en) A drawback of `RUM` is that it has slower build and insert times than `GIN`. This is because we need to store additional information besides keys and because diff --git a/img/PGpro-logo.png b/img/PGpro-logo.png deleted file mode 100644 index 39cc6b8396..0000000000 Binary files a/img/PGpro-logo.png and /dev/null differ diff --git a/img/PGpro-logo.svg b/img/PGpro-logo.svg new file mode 100644 index 0000000000..9a8ff03914 --- /dev/null +++ b/img/PGpro-logo.svg @@ -0,0 +1,17 @@ + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/img/gin_rum.png b/img/gin_rum.png deleted file mode 100644 index 48ab61747a..0000000000 Binary files a/img/gin_rum.png and /dev/null differ diff --git a/img/gin_rum.svg b/img/gin_rum.svg new file mode 100644 index 0000000000..fe928e8d45 --- /dev/null +++ b/img/gin_rum.svg @@ -0,0 +1,48 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +