Tom Lane d3f4e8a8a7 Avoid formally-undefined use of memcpy() in hstoreUniquePairs(). ... hstoreUniquePairs() often called memcpy with equal source and destination pointers. Although this is almost surely harmless in practice, it's undefined according to the letter of the C standard. Some versions of valgrind will complain about it, and some versions of libc as well (cf. commit ad520ec4a). Tweak the code to avoid doing that. Noted by Tomas Vondra. Back-patch to all supported versions because of the hazard of libc assertions. Discussion: https://postgr.es/m/bf84d940-90d4-de91-19dd-612e011007f4@fuzzy.cz		2017-11-25 14:42:10 -05:00
..
data
expected
sql
.gitignore
hstore_compat.c
hstore_gin.c	Make DatumGetFoo/PG_GETARG_FOO/PG_RETURN_FOO macro names more consistent.	2017-09-18 15:21:23 -04:00
hstore_gist.c	Change TRUE/FALSE to true/false	2017-11-08 11:37:28 -05:00
hstore_io.c	Avoid formally-undefined use of memcpy() in hstoreUniquePairs().	2017-11-25 14:42:10 -05:00
hstore_op.c	Make DatumGetFoo/PG_GETARG_FOO/PG_RETURN_FOO macro names more consistent.	2017-09-18 15:21:23 -04:00
hstore--1.0--1.1.sql
hstore--1.1--1.2.sql
hstore--1.2--1.3.sql
hstore--1.3--1.4.sql
hstore--1.4--1.5.sql
hstore--1.4.sql
hstore--unpackaged--1.0.sql
hstore.control
hstore.h	Make DatumGetFoo/PG_GETARG_FOO/PG_RETURN_FOO macro names more consistent.	2017-09-18 15:21:23 -04:00
Makefile