From 43a134f28b350c4b731db9dddf2f53c407a7077f Mon Sep 17 00:00:00 2001 From: Daniel Gustafsson Date: Mon, 1 Nov 2021 22:42:49 +0100 Subject: Replace unicode characters in comments with ascii The unicode characters, while in comments and not code, caused MSVC to emit compiler warning C4819: The file contains a character that cannot be represented in the current code page (number). Save the file in Unicode format to prevent data loss. Fix by replacing the characters in print.c with descriptive comments containing the codepoints and symbol names, and remove the character in brin_bloom.c which was a footnote reference copied from the paper citation. Per report from hamerkop in the buildfarm. Reviewed-by: Tom Lane Discussion: https://postgr.es/m/340E4118-0D0C-4E85-8141-8C40EB22DA3A@yesql.se --- src/backend/access/brin/brin_bloom.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/backend') diff --git a/src/backend/access/brin/brin_bloom.c b/src/backend/access/brin/brin_bloom.c index 2c8a20aaca6..09b8d04a46a 100644 --- a/src/backend/access/brin/brin_bloom.c +++ b/src/backend/access/brin/brin_bloom.c @@ -49,7 +49,7 @@ * We use a scheme requiring only two functions described in this paper: * * Less Hashing, Same Performance:Building a Better Bloom Filter - * Adam Kirsch, Michael Mitzenmacher†, Harvard School of Engineering and + * Adam Kirsch, Michael Mitzenmacher, Harvard School of Engineering and * Applied Sciences, Cambridge, Massachusetts [DOI 10.1002/rsa.20208] * * The two hash functions h1 and h2 are calculated using hard-coded seeds, -- cgit v1.2.3