Re: pg_get_tabledef
От | Usama Munir |
---|---|
Тема | Re: pg_get_tabledef |
Дата | |
Msg-id | 4651E0B4.2020908@enterprisedb.com обсуждение исходный текст |
Ответ на | Re: pg_get_tabledef (Andrew Dunstan <andrew@dunslane.net>) |
Ответы |
Re: pg_get_tabledef
|
Список | pgsql-hackers |
When you say pgdump library, do you mean taking all catalog querying functionality into a contrib like module , exposed as functions and then have a simple pgdump executable which calls those functions to dump to a file, because you would still need a pgdump executable i suppose for people to be able to backup their stuff. Is my understanding somewhere near actual idea or i am way off here? Are there any discussions on this topic which could give me a little more idea? because i would definitely like to take a shot at this. Regards, Usama Munir EnterpriseDB (www.enterprisedb.com) Andrew Dunstan wrote: > > > Usama Munir wrote: >> I think using pg_dump in some cases is a good option , but not all >> the time, having a function makes it much cleaner to use > > That's why having a shared pgdump library as has been previously > mentioned is by far the best solution. > > We have discussed this before, and factoring out this functionality > into a shared lib is what needs to be done. I'm not convinced it is as > much work as Tom suggests, but it is certainly a non-trivial task. > > cheers > > andrew
В списке pgsql-hackers по дате отправления: