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

Re: pgsql: In pg_upgrade, copy fsm, vm, and extent files by checking for fi

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: In pg_upgrade, copy fsm, vm, and extent files by checking for fi
Date: 2012-11-14 23:15:30
Message-ID: 28536.1352934930@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Wed, Nov 14, 2012 at 05:39:29PM -0500, Tom Lane wrote:
>> You would have been better off keeping the array and sorting it so you
>> could use binary search, instead of passing the problem off to the
>> filesystem.

> Well, testing showed using open() was a big win.

... on the filesystem you tested on.  I'm concerned that it might not
look so good on other platforms.

			regards, tom lane


In response to

Responses

pgsql-hackers by date

Next:From: Jeff DavisDate: 2012-11-14 23:24:17
Subject: Re: Enabling Checksums
Previous:From: Bruce MomjianDate: 2012-11-14 22:58:14
Subject: Re: pgsql: In pg_upgrade, copy fsm, vm, and extent files by checking for fi

pgsql-committers by date

Next:From: Bruce MomjianDate: 2012-11-14 23:28:41
Subject: Re: pgsql: In pg_upgrade, copy fsm, vm, and extent files by checking for fi
Previous:From: Bruce MomjianDate: 2012-11-14 22:58:14
Subject: Re: pgsql: In pg_upgrade, copy fsm, vm, and extent files by checking for fi

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