Fix typo in comment, and reword it slightly while we're at it.
Branch
--
REL9_2_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/a846f63aed825e4addbf2436fc0de9ddf568
Modified Files
--
src/backend/access/transam/xlog.c |4 ++--
1 files changed, 2
Fix typo in comment, and reword it slightly while we're at it.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/1a956481baa2bb53d9510bb14cf64bb5faad29fb
Modified Files
--
src/backend/access/transam/xlog.c |4 ++--
1 files changed, 2 insertions(+), 2
Fix permissions explanations in CREATE DATABASE and CREATE SCHEMA docs.
These reference pages still claimed that you have to be superuser to create
a database or schema owned by a different role. That was true before 8.1,
but it was changed in commits aa1110624c08298393dfce996f7b21809d98d3fd and
Fix permissions explanations in CREATE DATABASE and CREATE SCHEMA docs.
These reference pages still claimed that you have to be superuser to create
a database or schema owned by a different role. That was true before 8.1,
but it was changed in commits aa1110624c08298393dfce996f7b21809d98d3fd and
Fix permissions explanations in CREATE DATABASE and CREATE SCHEMA docs.
These reference pages still claimed that you have to be superuser to create
a database or schema owned by a different role. That was true before 8.1,
but it was changed in commits aa1110624c08298393dfce996f7b21809d98d3fd and
Fix permissions explanations in CREATE DATABASE and CREATE SCHEMA docs.
These reference pages still claimed that you have to be superuser to create
a database or schema owned by a different role. That was true before 8.1,
but it was changed in commits aa1110624c08298393dfce996f7b21809d98d3fd and
Fix permissions explanations in CREATE DATABASE and CREATE SCHEMA docs.
These reference pages still claimed that you have to be superuser to create
a database or schema owned by a different role. That was true before 8.1,
but it was changed in commits aa1110624c08298393dfce996f7b21809d98d3fd and
Fix permissions explanations in CREATE DATABASE and CREATE SCHEMA docs.
These reference pages still claimed that you have to be superuser to create
a database or schema owned by a different role. That was true before 8.1,
but it was changed in commits aa1110624c08298393dfce996f7b21809d98d3fd and
Fix parse location tracking for lists that can be empty.
The previous coding of the YYLLOC_DEFAULT macro behaved strangely for empty
productions, assigning the previous nonterminal's location as the parse
location of the result. The usefulness of that was (at best) debatable
already, but the
Make CREATE AGGREGATE complain if the initcond is invalid for the datatype.
The initial transition value is stored as a text string and not fed to the
transition type's input function until runtime (so that values such as
now don't get frozen at creation time). Previously, CREATE AGGREGATE
Remove redundant code for getnameinfo() replacement
Our getnameinfo() replacement implementation in getaddrinfo.c failed
unless NI_NUMERICHOST and NI_NUMERICSERV were given as flags, because
it doesn't resolve host names, only numeric IPs. But per standard,
when those flags are not given, an
PL/pgSQL: rename gram.y to pl_gram.y
This makes the naming inside plpgsql consistent and distinguishes the
file from the backend's gram.y file. It will also allow easier
refactoring of the bison make rules later on.
Branch
--
master
Details
---
getnameinfo_unix has to be taught not to insist on NI_NUMERIC flags, too.
Per testing of previous patch.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/1997f34db4687e671690ed054c8f30bb501b1168
Modified Files
--
src/backend/libpq/ip.c |5 -
1
On Tue, 2012-10-02 at 17:05 +0100, Peter Geoghegan wrote:
On 30 September 2012 01:07, Peter Eisentraut pete...@gmx.net wrote:
Disable _FORTIFY_SOURCE with ICC
I'm having some problems of my own with this. Specifically:
gcc -O0 -g -Wall -Wmissing-prototypes -Wpointer-arith
14 matches
Mail list logo