| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(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:28:41 |
| Message-ID: | 20121114232841.GC6753@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Wed, Nov 14, 2012 at 06:15:30PM -0500, Tom Lane wrote:
> 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.
True. I am on ext3. So I need to generate a proof-of-concept patch and
have others test it?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-11-14 23:57:13 | Re: pgsql: In pg_upgrade, copy fsm, vm, and extent files by checking for fi |
| Previous Message | Tom Lane | 2012-11-14 23:15:30 | Re: pgsql: In pg_upgrade, copy fsm, vm, and extent files by checking for fi |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2012-11-14 23:55:52 | Re: Pg_upgrade speed for many tables |
| Previous Message | Jeff Davis | 2012-11-14 23:24:17 | Re: Enabling Checksums |