Skip to content

Commit 3716cee

Browse files
committed
master merged, conflict resolved
2 parents 1ff5c83 + c24c1de commit 3716cee

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ sudo make uninstall
5757

5858
## Usage
5959

60-
First ZSON should be *trained* on common data using zson_learn procedure:
60+
First ZSON should be *trained* on common data using zson\_learn procedure:
6161

6262
```
6363
zson_learn(
@@ -107,7 +107,7 @@ select zson_learn('{{"table1", "col1"}, {"table2", "col2"}}');
107107

108108
This time *second* dictionary will be created. Dictionaries are cached in memory so it will take about a minute before ZSON realizes that there is a new dictionary. After that old documents will be decompressed using the old dictionary and new documents will be compressed and decompressed using the new dictionary.
109109

110-
To find out which dictionary is used for a given ZSON document use zson_info procedure:
110+
To find out which dictionary is used for a given ZSON document use zson\_info procedure:
111111

112112
```
113113
zson_test=# select zson_info(x) from test_compress where id = 1;
@@ -139,5 +139,5 @@ select pg_table_size('tt') / (select count(*) from tt)
139139

140140
... i.e. average document size. When it suddenly starts to grow it's time to re-learn.
141141

142-
However, developers usually know when they change a schema significantly. It's also easy to re-check whether current schema differs a lot from the original using zson_dict table.
142+
However, developers usually know when they change a schema significantly. It's also easy to re-check whether current schema differs a lot from the original using zson\_dict table.
143143

0 commit comments

Comments
 (0)