Remove set-but-not-used variables.
Reported by both Peter Eisentraunt and Kevin Grittner.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/fba60e573e092991dde4f757b88384ab1ec6a0ce
Modified Files
--
src/backend/executor/tqueue.c |4
1 file changed,
Update 9.5 release notes through today.
Branch
--
REL9_5_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/5daafafe74e23f9e6a8971820b4233565a837b77
Modified Files
--
doc/src/sgml/release-9.5.sgml |8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
--
S
Update 9.5 release notes through today.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/ad9fad7b68c4209db7d73f59a538ffe619c07872
Modified Files
--
doc/src/sgml/release-9.5.sgml |8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
--
Sent via
Add "xid <> xid" and "xid <> int4" operators.
The corresponding "=" operators have been there a long time, and not
having their negators is a bit of a nuisance.
Michael Paquier
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/c5e86ea932794051d2fe3bd26ce4c03981b0b826
Rename PQsslAttributes() to PQsslAttributeNames(), and const-ify fully.
Per discussion, the original name was a bit misleading, and
PQsslAttributeNames() seems more apropos. It's not quite too late to
change this in 9.5, so let's change it while we can.
Also, make sure that the pointer array is
Rename PQsslAttributes() to PQsslAttributeNames(), and const-ify fully.
Per discussion, the original name was a bit misleading, and
PQsslAttributeNames() seems more apropos. It's not quite too late to
change this in 9.5, so let's change it while we can.
Also, make sure that the pointer array is
On Friday, November 6, 2015 3:59 PM, Robert Haas wrote:
> Modified Files
> --
> src/backend/executor/tqueue.c| 983 -
This patch created some referenced local variables:
tqueue.c: In function ‘tqueueReceiveSlot’:
tqueue.c:124:18: error: varia
Fix enforcement of restrictions inside regexp lookaround constraints.
Lookahead and lookbehind constraints aren't allowed to contain backrefs,
and parentheses within them are always considered non-capturing. Or so
says the manual. But the regexp parser forgot about these rules once
inside a pare
Fix enforcement of restrictions inside regexp lookaround constraints.
Lookahead and lookbehind constraints aren't allowed to contain backrefs,
and parentheses within them are always considered non-capturing. Or so
says the manual. But the regexp parser forgot about these rules once
inside a pare
Fix enforcement of restrictions inside regexp lookaround constraints.
Lookahead and lookbehind constraints aren't allowed to contain backrefs,
and parentheses within them are always considered non-capturing. Or so
says the manual. But the regexp parser forgot about these rules once
inside a pare
Fix enforcement of restrictions inside regexp lookaround constraints.
Lookahead and lookbehind constraints aren't allowed to contain backrefs,
and parentheses within them are always considered non-capturing. Or so
says the manual. But the regexp parser forgot about these rules once
inside a pare
Fix enforcement of restrictions inside regexp lookaround constraints.
Lookahead and lookbehind constraints aren't allowed to contain backrefs,
and parentheses within them are always considered non-capturing. Or so
says the manual. But the regexp parser forgot about these rules once
inside a pare
Fix enforcement of restrictions inside regexp lookaround constraints.
Lookahead and lookbehind constraints aren't allowed to contain backrefs,
and parentheses within them are always considered non-capturing. Or so
says the manual. But the regexp parser forgot about these rules once
inside a pare
On 11/6/15 11:06 PM, Robert Haas wrote:
> Try to convince gcc that TupleQueueRemap never falls off the end.
>
> Without this, MacOS gcc version 4.2.1 isn't convinced.
I still see some compiler warnings from this:
tqueue.c: In function ‘tqueueReceiveSlot’:
tqueue.c:124:18: warning: variable ‘tup’
14 matches
Mail list logo
