Tom,
Can you please suggest a good practice how to propagate such DB
settings into dumps?
I also suffer from this: my DB currently have 5 schemas and
application strongly depends on the search_path. I cannot dump whole
cluster, I need only 1 specific database. At this moment I use ugly
solution
On 10/9/06, Nikolay Samokhvalov <[EMAIL PROTECTED]> wrote:
Maybe my understanding is wrong - I'll be glad to hear why.
Maybe at least to create special switcher for database settings? (It
would remain backward compatibility...)
--
Best regards,
Nikolay
---(end of broad
On 10/9/06, Tom Lane <[EMAIL PROTECTED]> wrote:
Duplication of code and functionality with pg_dumpall.
Well, then "-C" option of pg_dump can be considered as duplication of
pg_dumpall's functionality too, right?
I'd want to see
some thought about how to resolve that, not just a quick copy-som
"Nikolay Samokhvalov" <[EMAIL PROTECTED]> writes:
> What is the reason to not include database settings (like search_path)
> to database dump created with "pg_dump -C"?
Duplication of code and functionality with pg_dumpall. I'd want to see
some thought about how to resolve that, not just a quick
