You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 7, 2023. It is now read-only.
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,
^
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The text was updated successfully, but these errors were encountered: