diff options
| author | Thomas Munro <tmunro@postgresql.org> | 2024-07-30 21:45:01 +1200 |
|---|---|---|
| committer | Thomas Munro <tmunro@postgresql.org> | 2024-07-30 22:58:37 +1200 |
| commit | e25626677f8076eb3ce94586136c5464ee154381 (patch) | |
| tree | f03f87af97b998e2dd5aadcfe8a93a83a1ae716b /doc/src | |
| parent | 1330843bb78e9d2422af2f2b9909b80732bd6fc0 (diff) | |
| download | postgresql-e25626677f8076eb3ce94586136c5464ee154381.tar.gz postgresql-e25626677f8076eb3ce94586136c5464ee154381.zip | |
Remove --disable-spinlocks.
A later change will require atomic support, so it wouldn't make sense
for a hypothetical new system not to be able to implement spinlocks.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us> (concept, not the patch)
Reviewed-by: Andres Freund <andres@anarazel.de> (concept, not the patch)
Discussion: https://postgr.es/m/3351991.1697728588%40sss.pgh.pa.us
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/installation.sgml | 37 |
1 files changed, 1 insertions, 36 deletions
diff --git a/doc/src/sgml/installation.sgml b/doc/src/sgml/installation.sgml index 4784834ab9f..3f19f272b17 100644 --- a/doc/src/sgml/installation.sgml +++ b/doc/src/sgml/installation.sgml @@ -1258,22 +1258,6 @@ build-postgresql: </listitem> </varlistentry> - <varlistentry id="configure-option-disable-spinlocks"> - <term><option>--disable-spinlocks</option></term> - <listitem> - <para> - Allow the build to succeed even if <productname>PostgreSQL</productname> - has no CPU spinlock support for the platform. The lack of - spinlock support will result in very poor performance; therefore, - this option should only be used if the build aborts and - informs you that the platform lacks spinlock support. If this - option is required to build <productname>PostgreSQL</productname> on - your platform, please report the problem to the - <productname>PostgreSQL</productname> developers. - </para> - </listitem> - </varlistentry> - <varlistentry id="configure-option-disable-atomics"> <term><option>--disable-atomics</option></term> <listitem> @@ -2690,23 +2674,6 @@ ninja install </listitem> </varlistentry> - <varlistentry id="configure-spinlocks-meson"> - <term><option>-Dspinlocks={ true | false }</option></term> - <listitem> - <para> - This option is set to true by default; setting it to false will - allow the build to succeed even if <productname>PostgreSQL</productname> - has no CPU spinlock support for the platform. The lack of - spinlock support will result in very poor performance; therefore, - this option should only be changed if the build aborts and - informs you that the platform lacks spinlock support. If setting this - option to false is required to build <productname>PostgreSQL</productname> on - your platform, please report the problem to the - <productname>PostgreSQL</productname> developers. - </para> - </listitem> - </varlistentry> - <varlistentry id="configure-atomics-meson"> <term><option>-Datomics={ true | false }</option></term> <listitem> @@ -2719,6 +2686,7 @@ ninja install </para> </listitem> </varlistentry> + </variablelist> </sect3> @@ -3393,9 +3361,6 @@ export MANPATH these CPU architectures: x86, PowerPC, S/390, SPARC, ARM, MIPS, and RISC-V, including big-endian, little-endian, 32-bit, and 64-bit variants where applicable. - It is often - possible to build on an unsupported CPU type by configuring with - <option>--disable-spinlocks</option>, but performance will be poor. </para> <para> |