Postgres Pro
Downloads
Home   >   mailing lists

Re: pg_dump without explicit table locking - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_dump without explicit table locking
Date
Msg-id 10756.1395098150@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_dump without explicit table locking  (Jim Nasby <jim@nasby.net>)
Responses Re: pg_dump without explicit table locking  (Joe Conway <mail@joeconway.com>)
Re: pg_dump without explicit table locking  (Jürgen Strobel <juergen+pg@strobel.info>)
List pgsql-hackers
Tree view 
Jim Nasby <jim@nasby.net> writes:
> On 3/17/14, 8:47 AM, Tom Lane wrote:
>> (Note that this is only one of assorted O(N^2) behaviors in older versions
>> of pg_dump; we've gradually stamped them out over time.)

> On that note, it's recommended that when you are taking a backup to restore into a newer version of Postgres you
createthe dump using the NEWER version of pg_dump, not the old one.
 

Right.  IIRC, the OP said he *did* use a recent pg_dump ... but this
particular issue got fixed server-side, so the new pg_dump didn't help
against an 8.1 server :-(
        regards, tom lane

pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: pg_dump without explicit table locking
Next
From: Joe Conway
Date:
Subject: Re: pg_dump without explicit table locking