Clean up icc + ia64 situation.
Some googling turned up multiple sources saying that older versions of icc
do not accept gcc-compatible asm blocks on IA64, though asm does work on
x86[_64]. This is apparently fixed as of icc version 12.0 or so, but that
doesn't help us much; if we have to carry th
docs: remove outdated note about unique indexes
Patch by Josh Kupershmidt
Backpatch through 9.5
Branch
--
REL9_5_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/06502185d8352258560b7fad82571d159dff8658
Modified Files
--
doc/src/sgml/indices.sgml |6 +-
1
docs: remove outdated note about unique indexes
Patch by Josh Kupershmidt
Backpatch through 9.5
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/049a7799dfce096923da27a9b0e4a3c7a0a47104
Modified Files
--
doc/src/sgml/indices.sgml |6 +-
1 file ch
Allow icc to use the same atomics infrastructure as gcc.
The atomics headers were written under the impression that icc doesn't
handle gcc-style asm blocks, but this is demonstrably false on x86_[64],
because s_lock.h has done it that way for more than a decade. (The jury is
still out on whether
Actually, it's not that hard to merge the Windows pqsignal code ...
... just need to typedef sigset_t and provide sigemptyset/sigfillset,
which are easy enough.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/f333204bbcd32091311b070e8f8ab4717dd8cadf
Modified Files
-
Remove theoretically-unnecessary special case for icc.
Intel's icc is generally able to swallow asm blocks written for gcc.
We have a few places that don't seem to know that, though. Experiment
with removing the special case for icc in ia64_get_bsp(); if the buildfarm
likes this, I'll try more cl
Remove support for Unix systems without the POSIX signal APIs.
Remove configure's checks for HAVE_POSIX_SIGNALS, HAVE_SIGPROCMASK, and
HAVE_SIGSETJMP. These APIs are required by the Single Unix Spec v2
(POSIX 1997), which we generally consider to define our minimum required
set of Unix APIs. Mor
psql: print longtable as a possible \pset option
For some reason this message was not updated when the longtable option
was added.
Backpatch through 9.3
Branch
--
REL9_3_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/a7f8e306d2af5b497077a0dc1bfd2cb27aa232f4
Modified Files
psql: print longtable as a possible \pset option
For some reason this message was not updated when the longtable option
was added.
Backpatch through 9.3
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/8f7d044ba842ab3359a8a3190ff2f3aa1de2a6bb
Modified Files
---
psql: print longtable as a possible \pset option
For some reason this message was not updated when the longtable option
was added.
Backpatch through 9.3
Branch
--
REL9_5_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/bda58e98d535762b46a9d6315f4e49d9c93e81d8
Modified Files
psql: print longtable as a possible \pset option
For some reason this message was not updated when the longtable option
was added.
Backpatch through 9.3
Branch
--
REL9_4_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/ce6e50aebe5d0874d64767b8963b162fdc186fa7
Modified Files
Small grammar fix
Josh Kupershmidt
Branch
--
REL9_5_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/bafeb010b2500b31d303f4c2879cec54481dafdd
Modified Files
--
doc/src/sgml/pgprewarm.sgml |8
1 file changed, 4 insertions(+), 4 deletions(-)
--
Sent vi
Small grammar fix
Josh Kupershmidt
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/93370076c40730ce2a9071c6a4694d6b0e5b2f0c
Modified Files
--
doc/src/sgml/pgprewarm.sgml |8
1 file changed, 4 insertions(+), 4 deletions(-)
--
Sent via pgsql
13 matches
Mail list logo