pg_dump -C option
От | Jim Buttafuoco |
---|---|
Тема | pg_dump -C option |
Дата | |
Msg-id | 200109091250.f89CoXJ11878@dual.buttafuoco.net обсуждение исходный текст |
Ответы |
Re: pg_dump -C option
|
Список | pgsql-hackers |
All, I am working a some patches to the code and I noticed that "pg_dump -C database" doesn't provide the database location information in the dump file. Is this correct? Thanks Jim Example: datname | datdba | encoding | datistemplate | datallowconn | datlastsysoid | datpath | idxpath -----------+--------+----------+---------------+--------------+---------------+---------+---------jb1 | 5433 | 0 | f | t | 18540 | | PGIDX1template1 | 5433 | 0 | t | t | 18540 | | template0 | 5433 | 0 | t | f | 18540 | | jb2 | 5433 | 0 | f | t | 18540 | PGDATA1 | PGIDX1jb3 | 5433 | 0 | f | t | 18540 | PGDATA1 | 4051 | 5433 | 0 | f | t | 18540 | PGDATA1 | PGIDX1 (Please ignore the IDXPATH column for now as I am trying to add support for INDEX locations as I am running out of room on my current system and I don't like the "symlink your own tables/index files" idea) and the output of pg_dump -C -- -- Selected TOC Entries: -- \connect - pgtest -- -- TOC Entry ID 1 (OID 0) -- -- Name: jb2 Type: DATABASE Owner: pgtest -- Create Database "jb2"; \connect jb2 pgtest
В списке pgsql-hackers по дате отправления: