Re: pg_dump additional options for performance
От | Simon Riggs |
---|---|
Тема | Re: pg_dump additional options for performance |
Дата | |
Msg-id | 1216620687.19656.860.camel@ebony.2ndQuadrant обсуждение исходный текст |
Ответ на | Re: pg_dump additional options for performance (Stephen Frost <sfrost@snowman.net>) |
Ответы |
Re: pg_dump additional options for performance
|
Список | pgsql-patches |
On Sun, 2008-07-20 at 21:18 -0400, Stephen Frost wrote: > * Simon Riggs (simon@2ndquadrant.com) wrote: > > On Sun, 2008-07-20 at 17:43 -0400, Stephen Frost wrote: > > > Even this doesn't cover everything though- it's too focused on tables > > > and data loading. Where do functions go? What about types? > > > > Yes, it is focused on tables and data loading. What about > > functions/types? No relevance here. > > I don't see how they're not relevant, it's not like they're being > excluded and in fact they show up in the pre-load output. Heck, even if > they *were* excluded, that should be made clear in the documentation > (either be an explicit include list, or saying they're excluded). > > Part of what's driving this is making sure we have a plan for future > objects and where they'll go. Perhaps it would be enough to just say > "pre-load is everything in the schema, except things which are faster > done in bulk (eg: indexes, keys)". I don't think it's right to say > pre-load is "only object definitions required to load data" when it > includes functions and ACLs though. > > Hopefully my suggestion and these comments will get us to a happy > middle-ground. I don't really understand what you're saying. The options split the dump into 3 parts that's all: before the load, the load and after the load. --schema-pre-load says "Dumps exactly what <option>--schema-only</> would dump, but only those statements before the data load." What is it you are suggesting? I'm unclear. -- Simon Riggs www.2ndQuadrant.com PostgreSQL Training, Services and Support
В списке pgsql-patches по дате отправления: