![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
but when i do a: pg_dump -C uescc > uescc.sql it add the create statement for the database but not add appropiates alter database for the parameters i set search_path in this case. But, pg_dumpall does. a bug in pg_dump? |
#3
| |||
| |||
|
|
Jaime Casanova <systemguards (AT) yahoo (DOT) com> writes: but when i do a: pg_dump -C uescc > uescc.sql it add the create statement for the database but not add appropiates alter database for the parameters i set search_path in this case. But, pg_dumpall does. a bug in pg_dump? No. That functionality is assigned to pg_dumpall. |
#4
| |||
| |||
|
|
On Tue, Oct 19, 2004 at 02:25:35PM -0400, Tom Lane wrote: Jaime Casanova <systemguards (AT) yahoo (DOT) com> writes: but when i do a: pg_dump -C uescc > uescc.sql it add the create statement for the database but not add appropiates alter database for the parameters i set search_path in this case. But, pg_dumpall does. a bug in pg_dump? No. That functionality is assigned to pg_dumpall. |
|
There doesn't seem to be a way of extracting only database creation from pg_dumpall. Or the schema of a single database, for example. There _is_ a functionality gap here. ISTM pg_dump -C (which dumps CREATE DATABASE) should dump ALTER DATABASE commands too. |
![]() |
| Thread Tools | |
| Display Modes | |
| |