[
https://issues.apache.org/jira/browse/HAWQ-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ruilong Huo resolved HAWQ-488.
------------------------------
Resolution: Fixed
> Cannot drop schema madlib and re-deploy MADlib in schema madlib
> ---------------------------------------------------------------
>
> Key: HAWQ-488
> URL: https://issues.apache.org/jira/browse/HAWQ-488
> Project: Apache HAWQ
> Issue Type: Bug
> Components: DDL
> Affects Versions: 2.0.0-beta-incubating
> Reporter: Ruilong Huo
> Assignee: Ruilong Huo
> Fix For: 2.0.0
>
>
> We have two problems here:
> 1. Cannot drop schema madlib and re-deploy MADlib in schema madlib
> 2. pg_dump skip dumping content of schema madlib/retail_demo, which should be
> dumped by default actually. To skip dumping some schema, you can specify it
> in command line option of pg_dump. Details below:
> {noformat}
> [gpadmin@localhost bin]$ pg_dump --help
> pg_dump dumps a database as a text file or to other formats.
> Usage:
> pg_dump [OPTION]... [DBNAME]
> General options:
> -f, --file=FILENAME output file name
> -F, --format=c|t|p output file format (custom, tar, plain text)
> -i, --ignore-version proceed even when server version mismatches
> pg_dump version
> -v, --verbose verbose mode
> -Z, --compress=0-9 compression level for compressed formats
> --help show this help, then exit
> --version output version information, then exit
> Options controlling the output content:
> -a, --data-only dump only the data, not the schema
> -b, --blobs include large objects in dump
> -c, --clean clean (drop) schema prior to create
> -C, --create include commands to create database in dump
> -d, --inserts dump data as INSERT, rather than COPY, commands
> -D, --column-inserts dump data as INSERT commands with column names
> -E, --encoding=ENCODING dump the data in encoding ENCODING
> -n, --schema=SCHEMA dump the named schema(s) only
> -N, --exclude-schema=SCHEMA do NOT dump the named schema(s)
> -o, --oids include OIDs in dump
> -O, --no-owner skip restoration of object ownership
> in plain text format
> -s, --schema-only dump only the schema, no data
> -S, --superuser=NAME specify the superuser user name to use in
> plain text format
> -t, --table=TABLE dump only matching table(s) (or views or
> sequences)
> -T, --exclude-table=TABLE do NOT dump matching table(s) (or views or
> sequences)
> -x, --no-privileges do not dump privileges (grant/revoke)
> --disable-dollar-quoting disable dollar quoting, use SQL standard quoting
> --disable-triggers disable triggers during data-only restore
> --use-set-session-authorization
> use SESSION AUTHORIZATION commands instead of
> ALTER OWNER commands to set ownership
> --gp-syntax dump with Greenplum Database syntax (default if
> gpdb)
> --no-gp-syntax dump without Greenplum Database syntax (default
> if postgresql)
> Connection options:
> -h, --host=HOSTNAME database server host or socket directory
> -p, --port=PORT database server port number
> -U, --username=NAME connect as specified database user
> -W, --password force password prompt (should happen automatically)
> If no database name is supplied, then the PGDATABASE environment
> variable value is used.
> Report bugs to <[email protected]>.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
