Search Postgresql Archives

Re: nice'ing the postgres COPY backend process to make pg_dumps run more "softly"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Try this:   http://klicman.org/throttle/

Kiriakos


On Mar 19, 2012, at 12:06 AM, Aleksey Tsalolikhin wrote:

> Hi.  When pg_dump runs, our application becomes inoperative (too
> slow).  I was going to ask if nice'ing the postgres backend process
> that handles the COPY would help but I just realized probably the
> pg_dump takes out locks when it runs and nice'ing it would just make
> it run longer...
> 
> However the man page says "pg_dump does not block other users
> accessing the database  (readers  or writers)."  But if we run a
> pg_dump, the phone starts ringing, users are complaining that the web
> app is not working.
> 
> Would appreciate some pointer to help me reconcile these two
> apparently contradictory facts.
> 
> Best,
> -at
> 
> -- 
> Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general


-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux