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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-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
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-09-17 19:23:51 | Re: [HACKERS] Developer's Wiki |
Previous Message | Tom Lane | 2006-09-17 18:25:16 | Re: [HACKERS] Developer's Wiki |
From | Date | Subject | |
---|---|---|---|
Next Message | Dan Thomas | 2006-09-17 19:52:21 | Re: tiny patch to make vacuumdb -a's database order match pg_dumpall |
Previous Message | Andrew - Supernews | 2006-09-17 14:57:20 | Re: Timezone List |