| 239 | {{{ |
| 240 | -F format |
| 241 | --format=format |
| 242 | Selects the format of the output. format can be one of the following: |
| 243 | |
| 244 | p |
| 245 | plain |
| 246 | Output a plain-text SQL script file (the default). |
| 247 | |
| 248 | c |
| 249 | custom |
| 250 | Output a custom-format archive suitable for input into pg_restore. |
| 251 | Together with the directory output format, this is the most flexible |
| 252 | output format in that it allows manual selection and reordering of |
| 253 | archived items during restore. This format is also compressed by |
| 254 | default. |
| 255 | |
| 256 | d |
| 257 | directory |
| 258 | Output a directory-format archive suitable for input into |
| 259 | pg_restore. This will create a directory with one file for each |
| 260 | table and blob being dumped, plus a so-called Table of Contents file |
| 261 | describing the dumped objects in a machine-readable format that |
| 262 | pg_restore can read. A directory format archive can be manipulated |
| 263 | with standard Unix tools; for example, files in an uncompressed |
| 264 | archive can be compressed with the gzip tool. This format is |
| 265 | compressed by default and also supports parallel dumps. |
| 266 | |
| 267 | t |
| 268 | tar |
| 269 | Output a tar-format archive suitable for input into pg_restore. The |
| 270 | tar format is compatible with the directory format: extracting a |
| 271 | tar-format archive produces a valid directory-format archive. |
| 272 | However, the tar format does not support compression. Also, when |
| 273 | using tar format the relative order of table data items cannot be |
| 274 | changed during restore. |
| 275 | }}} |