Do not wait forever to acquire shared table locks at the beginning of the dump\&. Instead, fail if unable to lock a table within the specified
110
\fItimeout\fR\&. The timeout may be specified in any of the formats accepted by
111
SET statement_timeout\&. Allowed values vary depending on the server version you are dumping from, but an integer number of milliseconds is accepted by all versions since 7\&.3\&. This option is ignored when dumping from a pre\-7\&.3 server\&.
112
.RE
113
.PP
114
\fB\-\-no\-tablespaces\fR
115
.RS 4
116
Do not output commands to create tablespaces nor select tablespaces for objects\&. With this option, all objects will be created in whichever tablespace is the default during restore\&.
117
.RE
118
.PP
119
\fB\-\-no\-security\-label\fR
120
.RS 4
121
Do not dump security labels\&.
122
.RE
123
.PP
124
\fB\-\-no\-unlogged\-table\-data\fR
125
.RS 4
126
Do not dump the contents of unlogged tables\&. This option has no effect on whether or not the table definitions (schema) are dumped; it only suppresses dumping the table data\&.
127
.RE
128
.PP
129
107
\fB\-r\fR, \fB\-\-roles\-only\fR
130
108
.RS 4
131
109
Dump only roles, no databases or tablespaces\&.
173
151
This option is for use by in\-place upgrade utilities\&. Its use for other purposes is not recommended or supported\&. The behavior of the option may change in future releases without notice\&.
174
152
.RE
175
153
.PP
176
\fB\-\-inserts\fR
177
.RS 4
178
Dump data as
179
INSERT
180
commands (rather than
181
COPY)\&. This will make restoration very slow; it is mainly useful for making dumps that can be loaded into non\-PostgreSQL
182
databases\&. Note that the restore might fail altogether if you have rearranged column order\&. The
\fB\-S\fR, or preferably be careful to start the resulting script as a superuser\&.
210
177
.RE
211
178
.PP
179
\fB\-\-inserts\fR
180
.RS 4
181
Dump data as
182
INSERT
183
commands (rather than
184
COPY)\&. This will make restoration very slow; it is mainly useful for making dumps that can be loaded into non\-PostgreSQL
185
databases\&. Note that the restore might fail altogether if you have rearranged column order\&. The
186
\fB\-\-column\-inserts\fR
187
option is safer, though even slower\&.
188
.RE
189
.PP
190
\fB\-\-lock\-wait\-timeout=\fR\fB\fItimeout\fR\fR
191
.RS 4
192
Do not wait forever to acquire shared table locks at the beginning of the dump\&. Instead, fail if unable to lock a table within the specified
193
\fItimeout\fR\&. The timeout may be specified in any of the formats accepted by
194
SET statement_timeout\&. Allowed values vary depending on the server version you are dumping from, but an integer number of milliseconds is accepted by all versions since 7\&.3\&. This option is ignored when dumping from a pre\-7\&.3 server\&.
195
.RE
196
.PP
197
\fB\-\-no\-security\-labels\fR
198
.RS 4
199
Do not dump security labels\&.
200
.RE
201
.PP
202
\fB\-\-no\-tablespaces\fR
203
.RS 4
204
Do not output commands to create tablespaces nor select tablespaces for objects\&. With this option, all objects will be created in whichever tablespace is the default during restore\&.
205
.RE
206
.PP
207
\fB\-\-no\-unlogged\-table\-data\fR
208
.RS 4
209
Do not dump the contents of unlogged tables\&. This option has no effect on whether or not the table definitions (schema) are dumped; it only suppresses dumping the table data\&.
210
.RE
211
.PP
212
\fB\-\-quote\-all\-identifiers\fR
213
.RS 4
214
Force quoting of all identifiers\&. This may be useful when dumping a database for migration to a future version that may have introduced additional keywords\&.
215
.RE
216
.PP
212
217
\fB\-\-use\-set\-session\-authorization\fR
213
218
.RS 4
214
219
Output SQL\-standard
218
223
commands to determine object ownership\&. This makes the dump more standards compatible, but depending on the history of the objects in the dump, might not restore properly\&.
219
224
.RE
220
225
.PP
221
\fB\-\-quote\-all\-identifiers\fR
222
.RS 4
223
Force quoting of all identifiers\&. This may be useful when dumping a database for migration to a future version that may have introduced additional keywords\&.