Tom Lane 43ac12c6e6 In type_sanity, check I/O functions of built-in types are not volatile. ... We have a project policy that I/O functions must not be volatile, as per commit aab353a60b, but we weren't doing anything to enforce that. In most usage the marking of the function doesn't matter as long as its behavior is sane --- but I/O casts can expose the marking as user-visible behavior, as per today's complaint from Joe Van Dyk about contrib/ltree. This test as such will only protect us against future errors in built-in data types. To catch the same error in contrib or third-party types, perhaps we should make CREATE TYPE complain? But that's a separate issue from enforcing the policy for built-in types.		2014-10-23 15:59:40 -04:00
..
examples	Update copyright for 2014	2014-01-07 16:05:30 -05:00
isolation	Implement SKIP LOCKED for row-level locks	2014-10-07 17:23:34 -03:00
locale	Rename 'gmake' to 'make' in docs and recommended commands	2014-02-12 17:29:19 -05:00
mb	Lots of doc corrections.	2012-04-23 22:43:09 -04:00
performance	Run newly-configured perltidy script on Perl files.	2012-07-04 21:47:49 -04:00
perl	Handle old versions of Test::More	2014-09-10 20:52:35 -04:00
regress	In type_sanity, check I/O functions of built-in types are not volatile.	2014-10-23 15:59:40 -04:00
thread	Remove dependency on wsock32.lib in favor of ws2_32	2014-07-15 14:18:39 +02:00
Makefile	Add isolation test to check-world and installcheck-world	2012-03-05 20:19:20 +02:00