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
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers pgsql-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)



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

Attachment Content-Type Size
pg-dump-timeout.patch text/plain 5.1 KB

In response to


Browse pgsql-hackers by date

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

Browse pgsql-patches by date

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