diff options
| author | Greg Myers <gmyers@gitlab.com> | 2019-08-27 15:51:04 +0000 |
|---|---|---|
| committer | Greg Myers <gmyers@gitlab.com> | 2019-08-27 15:51:04 +0000 |
| commit | 51a0166af2c532aa7a0d04bb503b43499be97033 (patch) | |
| tree | 9ebd74e8518d573fe4860763ddb41146dab1f453 /doc/development/sha1_as_binary.md | |
| parent | f706677357fcdf9cd870d098379788543ea71058 (diff) | |
| parent | 27c222d16ccb666878c7ac558f484efa56f77f37 (diff) | |
| download | gitlab-ce-51a0166af2c532aa7a0d04bb503b43499be97033.tar.gz | |
Merge branch 'master' into 'api-curl-quote-url-docs'api-curl-quote-url-docs
# Conflicts:
# doc/api/events.md
Diffstat (limited to 'doc/development/sha1_as_binary.md')
| -rw-r--r-- | doc/development/sha1_as_binary.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/sha1_as_binary.md b/doc/development/sha1_as_binary.md index 3151cc29bbc..6c4252ec634 100644 --- a/doc/development/sha1_as_binary.md +++ b/doc/development/sha1_as_binary.md @@ -2,7 +2,7 @@ Storing SHA1 hashes as strings is not very space efficient. A SHA1 as a string requires at least 40 bytes, an additional byte to store the encoding, and -perhaps more space depending on the internals of PostgreSQL and MySQL. +perhaps more space depending on the internals of PostgreSQL. On the other hand, if one were to store a SHA1 as binary one would only need 20 bytes for the actual SHA1, and 1 or 4 bytes of additional space (again depending |