From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | "ktm(at)rice(dot)edu" <ktm(at)rice(dot)edu> |
Cc: | David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: PostgreSQL Dump rate is too slow |
Date: | 2015-01-08 18:03:52 |
Message-ID: | 20150108180352.GB1479@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
ktm(at)rice(dot)edu wrote:
> On Thu, Jan 08, 2015 at 08:38:37AM -0700, David G Johnston wrote:
> > On Thu, Jan 8, 2015 at 12:12 AM, Adalkonda Harshad [via PostgreSQL] <
> > ml-node+s1045698n5833283h97(at)n5(dot)nabble(dot)com> wrote:
> >
> > >
> > > As the database size is too large and tweaking few database parameters
> > > will result towards performance improvement on pg_dump to some extent and
> > > pg_dump -j option would have helped if the DB version is PostgreSQL 9.3 but
> > > unfortunately your DB version is PostgreSQL 9.2
> > >
> > pg_dump 9.3+ can be used against the 9.2 server without problems. Read
> > the documentation for the --jobs option for details.
>
> This is a nice option for allowing you to leverage more than a single CPU core
> for the dump, provided you have the CPU and I/O cycles to support it. As others
> have suggested, offloading to a replica can help with that.
Keep in mind, though, that while 9.3's pg_dump can read from a 9.2
server, there is no guarantee that what it writes will be readable by
9.2 other tools (pg_restore or psql). Maybe it is currently, but there
are no promises.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Ferrell, Denise CTR NSWCDD, Z11 | 2015-01-09 16:22:40 | PK/FK impacts using text data type |
Previous Message | ktm@rice.edu | 2015-01-08 15:44:04 | Re: PostgreSQL Dump rate is too slow |