Skip site navigation (1) Skip section navigation (2)

Re: pg_dump lock timeout

From: daveg <daveg(at)sonic(dot)net>
To: pgsql-patches(at)postgresql(dot)org
Cc: daveg(at)sonic(dot)net, hari(at)efrontier(dot)com
Subject: Re: pg_dump lock timeout
Date: 2008-07-17 02:44:07
Message-ID: 20080717024407.GL11471@sonic.net (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Here is an updated version of this patch against head. It builds, runs and
functions as expected. I did not build the sgml.

I've made changes based on various comments as follows:

  - use WAIT_TIME in description consistantly. Reworded for clarity.
    (Stephan Frost)

  - Use a separate query buffer in getTables() (Stephan Frost)
 
  - sets statement_timeout=0 afterwards per new policy (Tom Lane, Marko Kreen)

  - has only --long-option to conserve short option letters (Marko Kreen)

Regards

-dg

-- 
David Gould       daveg(at)sonic(dot)net      510 536 1443    510 282 0869
If simplicity worked, the world would be overrun with insects.

In response to

Responses

pgsql-hackers by date

Next:From: Sushant SinhaDate: 2008-07-17 03:01:46
Subject: small bug in hlCover
Previous:From: Bruce MomjianDate: 2008-07-17 01:34:29
Subject: Re: Change lock requirements for adding a trigger

pgsql-patches by date

Next:From: Tatsuo IshiiDate: 2008-07-17 08:56:50
Subject: Re: [PATCHES] WITH RECURSIVE updated to CVS TIP
Previous:From: Simon RiggsDate: 2008-07-16 16:55:39
Subject: Is autovacuum doing a wraparound-avoiding VACUUM?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group