When a postgres table has a custom type, it raises an error instead, because it doesn't recreate the custom type at the destination db.
huy@ks4003980:~$ pgcp -s demodb -d reporting -t public.bookings --force-schema demodb
I, [2015-11-08T11:49:17.926390 #14987] INFO -- : Start to copy from table public.bookings to table public.bookings
NOTICE: schema "demodb" already exists, skipping
I, [2015-11-08T11:49:21.963906 #14987] INFO -- : Destination table does not exist, creating destination table.
E, [2015-11-08T11:49:23.835802 #14987] ERROR -- : ERROR: type "taxi_types" does not exist
LINE 5: taxi_type taxi_types NULL,
^
When a postgres table has a custom type, it raises an error instead, because it doesn't recreate the custom type at the destination db.