From: | Jayashankar K B <Jayashankar(dot)KB(at)lnties(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Re: [PERFORM] Disable-spinlocks while compiling postgres 9.1 for ARM Cortex A8 |
Date: | 2012-02-26 12:16:05 |
Message-ID: | 1365276B7BDA4C40A519F0B4088230B309711198@POCITMSEXMB03.LntUniverse.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-performance |
Ok. I did a manual patch and it Postgres 9.1.1 compiled for me without using the --disable-spinlocks option.
Thanks a lot for the patch. :)
By the way, could you please point me to the explanation on the significance of spinlocks for Postgres?
Thanks and Regards
Jayashankar
-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: 25 February 2012 PM 12:54
To: Jayashankar K B
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] Re: [PERFORM] Disable-spinlocks while compiling postgres 9.1 for ARM Cortex A8
Jayashankar K B <Jayashankar(dot)KB(at)lnties(dot)com> writes:
> I tried to apply the patch. I succeeded in patching configure, configure.in and src/include/pg_config.h.in files.
> But while applying the patch for src/include/storage/s_lock.h , I am getting an error.
That patch should apply exactly to 9.1.0 or later. I think either you messed up copying the patch from the web page (note that patch is not forgiving about white space...) or else perhaps fooling with the file names messed it up. You shouldn't have to modify the file taken from the "patch" link at all. The right way to do it is to cd into the top source directory and use
patch -p1 <patchfile
which will tell patch how much of the filename to pay attention to (viz, not the "a/" or "b/" parts).
If you get too frustrated, just wait till Monday and grab 9.1.3.
regards, tom lane
Larsen & Toubro Limited
This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.
From | Date | Subject | |
---|---|---|---|
Next Message | Andy Colson | 2012-02-26 14:37:54 | Re: Four issues why "old elephants" lack performance: Explanation sought Four issues why "old elephants" lack performance: Explanation sought |
Previous Message | Dave Potts | 2012-02-26 09:17:53 | How to debugging a an external C function(IMMUTABLE STRICT ) |
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2012-02-26 13:55:11 | Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? |
Previous Message | Thomas Kellerer | 2012-02-26 11:46:03 | Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? |