Re: BUG #3682: Incomplete database restore
От | Tom Lane |
---|---|
Тема | Re: BUG #3682: Incomplete database restore |
Дата | |
Msg-id | 28892.1192998245@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: BUG #3682: Incomplete database restore ("Heikki Linnakangas" <heikki@enterprisedb.com>) |
Ответы |
Re: BUG #3682: Incomplete database restore
Re: BUG #3682: Incomplete database restore |
Список | pgsql-bugs |
"Heikki Linnakangas" <heikki@enterprisedb.com> writes: > Perhaps we should include the functionality of that script in pg_dump. I'm pretty uncomfortable with the notion of having pg_dump deliberately throw data away. Another problem is that even if we did that, it would only help people who dumped their old DB with 8.3 pg_dump. Having the functionality in pg_restore would be a little saner, but it still seems like a big wart. As for the datatype issue, I wonder whether we should just advise people to do CREATE DOMAIN public.tsvector AS pg_catalog.tsvector; before restoring? regards, tom lane
В списке pgsql-bugs по дате отправления: