Alvaro Herrera 7eca575d1c get_object_address: separate domain constraints from table constraints ... Apart from enabling comments on domain constraints, this enables a future project to replicate object dropping to remote servers: with the current mechanism there's no way to distinguish between the two types of constraints, so there's no way to know what to drop. Also added support for the domain constraint comments in psql's \dd and pg_dump. Catalog version bumped due to the change in ObjectType enum.		2014-12-23 09:06:44 -03:00
..
constraints.source	get_object_address: separate domain constraints from table constraints	2014-12-23 09:06:44 -03:00
copy.source
create_function_1.source	Make CREATE TYPE print warnings if a datatype's I/O functions are volatile.	2014-11-05 11:44:06 -05:00
create_function_2.source
largeobject.source
misc.source
tablespace.source	Use just one database connection in the "tablespace" test.	2014-11-12 07:33:17 -05:00