| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
| Cc: | amul sul <sulamul(at)gmail(dot)com>, Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>, David Steele <david(at)pgmasters(dot)net>, Greg Stark <stark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [POC] hash partitioning |
| Date: | 2017-05-16 17:23:13 |
| Message-ID: | CA+TgmoZkHOtEhcCudqZzEViAyuaOGFe4+zSnXpN3MyGVTAHm8g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, May 16, 2017 at 3:19 AM, Ashutosh Bapat
<ashutosh(dot)bapat(at)enterprisedb(dot)com> wrote:
> While earlier, I thought the same, I am wondering whether this is
> true. Don't different collations deem different strings equal e.g one
> collation may deem 'aa' and 'AA' as same but other may not.
No, that's not allowed. This has been discussed many times on this
mailing list. See varstr_cmp(), which you will notice refuses to
return 0 unless the strings are bytewise identical.
> Or is that
> encoding problem being discussed in hash functions thread?
No, that's something else entirely.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-05-16 17:26:14 | Re: [PATCH v2] Progress command to monitor progression of long running SQL queries |
| Previous Message | David Fetter | 2017-05-16 16:59:43 | Re: Hash Functions |