Fix whitespace
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/d11339c099fae036f4efffdc69d434c374c820b5
Modified Files
--
src/backend/utils/cache/relcache.c |4 ++--
src/include/port/atomics/generic-gcc.h |1 -
2 files changed, 2 insertions(+),
Define META_FREE in a way that doesn't cause -Wempty-body warnings.
That get rids of the only -Wempty-body warning when compiling postgres
with gcc 4.8/9. As 6550b901f shows, it's useful to be able to use that
option routinely.
Without asserts there's many more warnings, but that's food for
anoth
Fix atomic ops inline x86 inline assembly for older 32bit gccs.
Some x86 32bit versions of gcc apparently generate references to the
nonexistant %sil register when using when using the r input
constraint, but not with the =q constraint. The latter restricts
allocations to a/b/c/d which should all
Fix atomic ops for x86 gcc compilers that don't understand atomic intrinsics.
Per buildfarm animal locust.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/88bcdf9da5aa67da11ada0921703432ef2b7c21c
Modified Files
--
src/include/port/atomics/generic-gcc.h |
On Fri, Sep 26, 2014 at 9:16 AM, Andres Freund wrote:
> On 2014-09-26 09:12:43 +0900, Michael Paquier wrote:
>> On Fri, Sep 26, 2014 at 8:59 AM, Andres Freund wrote:
>> > Add a basic atomic ops API abstracting away platform/architecture details.
>>
>> locust is not happy with this patch:
>> http:
On 2014-09-26 09:12:43 +0900, Michael Paquier wrote:
> On Fri, Sep 26, 2014 at 8:59 AM, Andres Freund wrote:
> > Add a basic atomic ops API abstracting away platform/architecture details.
>
> locust is not happy with this patch:
> http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=locust&dt=2
On Fri, Sep 26, 2014 at 8:59 AM, Andres Freund wrote:
> Add a basic atomic ops API abstracting away platform/architecture details.
locust is not happy with this patch:
http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=locust&dt=2014-09-26%2000%3A00%3A48
Regards,
--
Michael
--
Sent via pg
Add a basic atomic ops API abstracting away platform/architecture details.
Several upcoming performance/scalability improvements require atomic
operations. This new API avoids the need to splatter compiler and
architecture dependent code over all the locations employing atomic
ops.
For several of
Remove ill-conceived ban on zero length json object keys.
We removed a similar ban on this in json_object recently, but the ban in
datum_to_json was left, which generate4d sprutious errors in othee json
generators, notable json_build_object.
Along the way, add an assertion that datum_to_json is n
Remove ill-conceived ban on zero length json object keys.
We removed a similar ban on this in json_object recently, but the ban in
datum_to_json was left, which generate4d sprutious errors in othee json
generators, notable json_build_object.
Along the way, add an assertion that datum_to_json is n
Change locking regimen around buffer replacement.
Previously, we used an lwlock that was held from the time we began
seeking a candidate buffer until the time when we found and pinned
one, which is disastrous for concurrency. Instead, use a spinlock
which is held just long enough to pop the freel
Refactor space allocation for base64 encoding/decoding in pgcrypto.
Instead of trying to accurately calculate the space needed, use a StringInfo
that's enlarged as needed. This is just moving things around currently - the
old code was not wrong - but this is in preparation for a patch that adds
su
Fix VPATH builds of the replication parser from git for some !gcc compilers.
Some compilers don't automatically search the current directory for
included files. 9cc2c182fc2 fixed that for builds from tarballs by
adding an include to the source directory. But that doesn't work when
the scanner is g
Fix VPATH builds of the replication parser from git for some !gcc compilers.
Some compilers don't automatically search the current directory for
included files. 9cc2c182fc2 fixed that for builds from tarballs by
adding an include to the source directory. But that doesn't work when
the scanner is g
Fix VPATH builds of the replication parser from git for some !gcc compilers.
Some compilers don't automatically search the current directory for
included files. 9cc2c182fc2 fixed that for builds from tarballs by
adding an include to the source directory. But that doesn't work when
the scanner is g
Fix VPATH builds of the replication parser from git for some !gcc compilers.
Some compilers don't automatically search the current directory for
included files. 9cc2c182fc2 fixed that for builds from tarballs by
adding an include to the source directory. But that doesn't work when
the scanner is g
Fix VPATH builds of the replication parser from git for some !gcc compilers.
Some compilers don't automatically search the current directory for
included files. 9cc2c182fc2 fixed that for builds from tarballs by
adding an include to the source directory. But that doesn't work when
the scanner is g
* Andres Freund (and...@2ndquadrant.com) wrote:
> I've not really looked at the code, but I doubt
> if (policy1->hassublinks != policy2->hassublinks);
> return false;
> was what you intended. Note the trailing ";".
Gah, quite right. Will fix.
Thanks!
On 2014-09-24 20:33:54 +, Stephen Frost wrote:
> Code review for row security.
>
> Buildfarm member tick identified an issue where the policies in the
> relcache for a relation were were being replaced underneath a running
> query, leading to segfaults while processing the policies to be added
Return NULL from json_object_agg if it gets no rows.
This makes it consistent with the docs and with all other builtin
aggregates apart from count().
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/ecacbdbcee67e202cfcaa1180da170b9f13654bb
Modified Files
Return NULL from json_object_agg if it gets no rows.
This makes it consistent with the docs and with all other builtin
aggregates apart from count().
Branch
--
REL9_4_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/bda1d14360404ef58c4647888032158991051b14
Modified Files
-
Add -D option to specify data directory to pg_controldata and pg_resetxlog.
It was confusing that to other commands, like initdb and postgres, you would
pass the data directory with "-D datadir", but pg_controldata and
pg_resetxlog would take just plain path, without the "-D". With this patch,
pg_
22 matches
Mail list logo
