| From: | Jürgen Strobel <juergen+pg(at)strobel(dot)info> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jim Nasby <jim(at)nasby(dot)net> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump without explicit table locking |
| Date: | 2014-03-18 10:02:38 |
| Message-ID: | 532819BE.2090901@strobel.info |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 18.03.14 00:15, Tom Lane wrote:
> Jim Nasby <jim(at)nasby(dot)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 create the 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 :-(
Yes, I did use 9.3's pg_dump against my 8.1 DB initially.
The patch was created against github's master.
-Jürgen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2014-03-18 10:02:46 | Re: gaussian distribution pgbench |
| Previous Message | KONDO Mitsumasa | 2014-03-18 09:57:04 | Re: gaussian distribution pgbench |