Robert Haas 463f2625a5 Support SECURITY LABEL on databases, tablespaces, and roles. ... This requires a new shared catalog, pg_shseclabel. Along the way, fix the security_label regression tests so that they don't monkey with the labels of any pre-existing objects. This is unlikely to matter in practice, since only the label for the "dummy" provider was being manipulated. But this way still seems cleaner. KaiGai Kohei, with fairly extensive hacking by me.		2011-07-20 13:18:24 -04:00
..
constraints.source	Reset reindex-in-progress state before reverifying an exclusion constraint.	2011-06-05 22:31:05 -04:00
copy.source	Remove useless whitespace at end of lines	2010-11-23 22:34:55 +02:00
create_function_1.source	Allow pg_regress to be run outside the build tree. Look for input files	2008-10-01 22:38:57 +00:00
create_function_2.source	Remove useless whitespace at end of lines	2010-11-23 22:34:55 +02:00
largeobject.source	Support hex-string input and output for type BYTEA.	2009-08-04 16:08:37 +00:00
misc.source	Fix toast table creation.	2011-04-13 18:17:52 -07:00
security_label.source	Support SECURITY LABEL on databases, tablespaces, and roles.	2011-07-20 13:18:24 -04:00
tablespace.source	Support ALTER TABLESPACE name SET/RESET ( tablespace_options ).	2010-01-05 21:54:00 +00:00