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

Re: tiny patch to make vacuumdb -a's database order match pg_dumpall

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgresql(dot)org, "Dan Thomas" <godders(at)gmail(dot)com>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: tiny patch to make vacuumdb -a's database order match pg_dumpall
Date: 2006-09-17 19:09:01
Message-ID: 23862.1158520141@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
"Dan Thomas" <godders(at)gmail(dot)com> writes:
> I've been having trouble running vacuumdb -a and pg_dumpall
> concurrently because they run through the databases in a different
> order (so dumpall was getting stuck behind vacuum's lock, and my
> firewall was rather unhelpfully closing the idle connection).

Um, whaddya mean "dumpall was getting stuck behind vacuum's lock"?
A plain vacuum doesn't take any locks that would block pg_dump.

While the proposed patch looks harmless enough, I'm unconvinced that
it will solve your problem, or even quite what the problem is.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2006-09-17 19:23:51
Subject: Re: [HACKERS] Developer's Wiki
Previous:From: Tom LaneDate: 2006-09-17 18:25:16
Subject: Re: [HACKERS] Developer's Wiki

pgsql-patches by date

Next:From: Dan ThomasDate: 2006-09-17 19:52:21
Subject: Re: tiny patch to make vacuumdb -a's database order match pg_dumpall
Previous:From: Andrew - SupernewsDate: 2006-09-17 14:57:20
Subject: Re: Timezone List

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