Hi Josua,
On Wed, Oct 7, 2009 at 6:29 PM, Joshua D. Drake wrote:
> On Wed, 2009-10-07 at 12:51 +0200, Loic d'Anterroches wrote:
>> Hello,
>
>> My problem is that the dump increased steadily with the number of
>> schemas (now about 20s from about 12s with 850 schemas) and pg_dump is
>> now balloon
On Wed, 2009-10-07 at 12:51 +0200, Loic d'Anterroches wrote:
> Hello,
> My problem is that the dump increased steadily with the number of
> schemas (now about 20s from about 12s with 850 schemas) and pg_dump is
> now ballooning at 120MB of memory usage when running the dump.
>
And it will contin
Harald,
>>settings up each time. The added benefit of doing a per schema dump is
>>that I provide it to the users directly, that way they have a full
>>export of their data.
>
> you should try the timing with
>
> pg_dump --format=c completedatabase.dmp
>
> and then generating the separte schemas
On Wed, Oct 7, 2009 at 5:54 PM, Bill Moran wrote:
> In response to "Loic d'Anterroches" :
>
>> On Wed, Oct 7, 2009 at 4:23 PM, Tom Lane wrote:
>> > "Loic d'Anterroches" writes:
>> >> Each night I am running:
>> >> pg_dump --blobs --schema=%s --no-acl -U postgres indefero | gzip >
>> >> /path/to/
Loic,
>settings up each time. The added benefit of doing a per schema dump is
>that I provide it to the users directly, that way they have a full
>export of their data.
you should try the timing with
pg_dump --format=c completedatabase.dmp
and then generating the separte schemas in an extra st
In response to "Loic d'Anterroches" :
> On Wed, Oct 7, 2009 at 4:23 PM, Tom Lane wrote:
> > "Loic d'Anterroches" writes:
> >> Each night I am running:
> >> pg_dump --blobs --schema=%s --no-acl -U postgres indefero | gzip >
> >> /path/to/backups/%s/%s-%s.sql.gz
> >> this for each installation, so
On Wed, Oct 7, 2009 at 4:23 PM, Tom Lane wrote:
> "Loic d'Anterroches" writes:
>> Each night I am running:
>> pg_dump --blobs --schema=%s --no-acl -U postgres indefero | gzip >
>> /path/to/backups/%s/%s-%s.sql.gz
>> this for each installation, so 1100 times. Substitution strings are to
>> timesta
"Loic d'Anterroches" writes:
> Each night I am running:
> pg_dump --blobs --schema=%s --no-acl -U postgres indefero | gzip >
> /path/to/backups/%s/%s-%s.sql.gz
> this for each installation, so 1100 times. Substitution strings are to
> timestamp and get the right schema.
This seems like a pretty d
Hello,
After a series of sessions to search the web for information, I am
asking the help of people having a bit more knowledge of the internals
of pg_dump to try to solve a performance problem I have. I am running
PostgreSQL version 8.3.8 both server and pg_dump,
The context is a farm hosting of
