| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, david(at)fetter(dot)org |
| Subject: | Re: MD5 aggregate |
| Date: | 2013-06-26 20:46:50 |
| Message-ID: | 51CB533A.6070603@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/26/13 4:04 PM, Dean Rasheed wrote:
> A quick google search reveals several people asking for something like
> this, and people recommending md5(string_agg(...)) or
> md5(string_agg(md5(...))) based solutions, which are doomed to failure
> on larger tables.
The thread discussed several other options of checksumming tables that
did not have the air of a crytographic offering, as Noah put it.
> So I think that there is a case for having md5_agg()
> in core as an alternative to such hacks, while having more
> sophisticated crypto functions available as extensions.
Well, in general, I'd rather see the sophisticated stuff in core and the
hacks in extensions.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Szymon Guz | 2013-06-26 20:47:47 | Re: [PATCH] Fix conversion for Decimal arguments in plpython functions |
| Previous Message | Jeff Janes | 2013-06-26 20:11:07 | Re: A better way than tweaking NTUP_PER_BUCKET |