Re: pg_dump resulting in excessive memory use by postmaster process

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Ben <ben(dot)fyvie(at)champsoftware(dot)com>
Cc: 'PG-General Mailing List' <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg_dump resulting in excessive memory use by postmaster process
Date: 2013-10-21 16:36:38
Message-ID: 20131021163638.GN2706@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Ben,

* Ben (ben(dot)fyvie(at)champsoftware(dot)com) wrote:
> When you say self-contained test case, what is it exactly that you're
> looking for? A script that builds out a DB with hundreds of
> schemas/relations, a pg_basebackup or something else?

Ideally, an SQL script that builds the DB and then a pg_dump command
that shows the high memory utilization. Based on the description of the
issue, the SQL script may need to only have the schema and not any of
the data. The point is that it's a self-contained set of scripts which
demonstrate the problem; iow, please put together the SQL script and the
pg_dump command, test that you still see the issue on a clean PG
instance, and then send those our way (if you're willing/able to share
the schema definition or whatever is necessary to replicate what you're
seeing).

Thanks!

Stephen

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Torsten Förtsch 2013-10-21 16:38:06 locks held during commit with synchronous replication
Previous Message Ben 2013-10-21 16:17:01 Re: pg_dump resulting in excessive memory use by postmaster process