Translation updates
Source-Git-URL: git://git.postgresql.org/git/pgtranslation/messages.git
Source-Git-Hash: 3b0ccc27cf917446ea0a6c680b70534cfcaba81e
Branch
--
REL9_5_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/00dfd5c94c41685e867e3a686900cc2f9e4dd829
Modified Files
-
Fix typo in comment.
Masahiko Sawada
Branch
--
REL9_5_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/fa39e891b08a5cb283a721592d0fa2c19b4c7176
Modified Files
--
src/bin/pg_rewind/RewindTest.pm |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
Sent via
Fix typo in comment.
Masahiko Sawada
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/8978eb03a8dcfafd9e0839bc430749839476c34a
Modified Files
--
src/bin/pg_rewind/RewindTest.pm |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
Sent via pgsql-c
Adjust behavior of row_security GUC to match the docs.
Some time back we agreed that row_security=off should not be a way to
bypass RLS entirely, but only a way to get an error if it was being
applied. However, the code failed to act that way for table owners.
Per discussion, this is a must-fix b
Adjust behavior of row_security GUC to match the docs.
Some time back we agreed that row_security=off should not be a way to
bypass RLS entirely, but only a way to get an error if it was being
applied. However, the code failed to act that way for table owners.
Per discussion, this is a must-fix b
Docs: provide a concrete discussion and example for RLS race conditions.
Commit 43cd468cf01007f3 added some wording to create_policy.sgml purporting
to warn users against a race condition of the sort that had been noted some
time ago by Peter Geoghegan. However, that warning was far too vague to
Docs: provide a concrete discussion and example for RLS race conditions.
Commit 43cd468cf01007f3 added some wording to create_policy.sgml purporting
to warn users against a race condition of the sort that had been noted some
time ago by Peter Geoghegan. However, that warning was far too vague to
Stamp 9.5.0.
Branch
--
REL9_5_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/cdd4ed5449bf317cc71b45a8deee0173822e7592
Modified Files
--
configure | 18 +-
configure.in |2 +-
doc/bug.template |
Fix treatment of *lpNumberOfBytesRecvd == 0: that's a completion condition.
pgwin32_recv() has treated a non-error return of zero bytes from WSARecv()
as being a reason to block ever since the current implementation was
introduced in commit a4c40f140d23cefb. However, so far as one can tell
from M
Fix treatment of *lpNumberOfBytesRecvd == 0: that's a completion condition.
pgwin32_recv() has treated a non-error return of zero bytes from WSARecv()
as being a reason to block ever since the current implementation was
introduced in commit a4c40f140d23cefb. However, so far as one can tell
from M
Fix treatment of *lpNumberOfBytesRecvd == 0: that's a completion condition.
pgwin32_recv() has treated a non-error return of zero bytes from WSARecv()
as being a reason to block ever since the current implementation was
introduced in commit a4c40f140d23cefb. However, so far as one can tell
from M
Fix treatment of *lpNumberOfBytesRecvd == 0: that's a completion condition.
pgwin32_recv() has treated a non-error return of zero bytes from WSARecv()
as being a reason to block ever since the current implementation was
introduced in commit a4c40f140d23cefb. However, so far as one can tell
from M
In psql's tab completion, change most TailMatches patterns to Matches.
In the refactoring in commit d37b816dc9e8f976c8913296781e08cbd45c5af1,
we mostly kept to the original design whereby only the last few words
on the line were matched to identify a completable pattern. However,
after commit d85
13 matches
Mail list logo
