| From: | Jeffrey Walton <noloader(at)gmail(dot)com> |
|---|---|
| To: | Jagmohan Kaintura <jagmohan(at)tecorelabs(dot)com> |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: murmur3 hash binary data migration from Oracle to PostgreSQL |
| Date: | 2023-04-25 03:22:11 |
| Message-ID: | CAH8yC8=UgYnHiV35OY4vRAqsYaa9BAbbr5gALhR2cnMy6mZyaA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Apr 24, 2023 at 9:22 PM Jagmohan Kaintura
<jagmohan(at)tecorelabs(dot)com> wrote:
>
> We are doing Migration from Oracle to PostgreSQL. In SOurce database we have Binary data stored using murmur3 hashing function. In Oracle this data is being generated from the Java code and inserted into the Oracle database.
>
> As part of Migration processes the reference data on which this murmur3 is generated is also getting changed while migrating to PostgreSQL.
>
> In PostgreSQL do we have any mechanism for fetching this murmur3 hash function for any UUID.
>
> Please let me know, what ever solution is available for the implementation.
My apologies if I misparsed a couple of statements. I am having
trouble determining if you are migrating away from Murmur3.
If you are selecting a new digest, then SipHash would be an excellent
choice. It was designed to avoid collisions and be fast. Plus it was
designed by Jean-Philippe Aumasson and Daniel J. Bernstein. It doesn't
get much better than those two fellows.
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zhijie Hou (Fujitsu) | 2023-04-25 03:57:59 | RE: Support logical replication of DDLs |
| Previous Message | Tom Lane | 2023-04-25 03:06:28 | Re: wiki.postgres Tighten trigger permission checks already resolved |