On Fri, Feb 17, 2017 at 11:34 AM, Thomas Munro
<thomas.mu...@enterprisedb.com> wrote:
> On Fri, Feb 17, 2017 at 7:02 AM, Robert Haas <rh...@postgresql.org> wrote:
>> http://git.postgresql.org/pg/commitdiff/9acb85597f1223ac26a5b19a9345849c43d0ff54
> Hmm. This will segfault
changed, 17 insertions(+)
Hmm. This will segfault if you're out of memory.
--
Thomas Munro
http://www.enterprisedb.com
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers
^~~~
/usr/include/stdint.h:153:20: note: expanded from macro 'SIZE_MAX'
#define SIZE_MAX UINT64_MAX
^~
/usr/include/stdint.h:87:27: note: expanded from macro 'UINT64_MAX'
#define UINT64_MAX18446744073709551615ULL
On Tue, Dec 6, 2016 at 12:44 AM, Heikki Linnakangas
<heikki.linnakan...@iki.fi> wrote:
> src/backend/storage/lmgr/lwlocknames.txt | 1 +
Missing one tab?
--
Thomas Munro
http://www.enterprisedb.com
whitespace.patch
Description: Binary data
--
Sent via pgsql-committer
on is now implemented as part of expression evaluation.
>
> This both leads to significant performance improvements, and makes
> future just-in-time compilation of expressions easier.
This is a huge achievement. Congratulations!
--
Thomas Munro
http://www.enterprisedb.com
--
Sent via
their use is discouraged
src/test/mb/expected/sjis.out:WARNING: hash indexes are not
WAL-logged and their use is discouraged
src/test/mb/expected/utf8.out:WARNING: hash indexes are not
WAL-logged and their use is discouraged
--
Thomas Munro
http://www.enterprisedb.com
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers
tails
> ---
> http://git.postgresql.org/pg/commitdiff/d31084e9d1118b25fd16580d9d8c2924b5740dff
This has broken VAX build farm members "poisson" and "davril". One
minor nitpick, I think it needs to rewritten in C so that pgindent can
handle it.
--
Thomas Munro
http://
the others I've talked about
recently [1][2].
[1]
https://www.postgresql.org/message-id/CAEepm=3da6ajyxiuk03pakt1t7egwann9cajc773ct1rdpo...@mail.gmail.com
[2]
https://www.postgresql.org/message-id/CAEepm=0b7ym9mzsviq1d-hnt4koarvejvsfayvfyknv-pvd...@mail.gmail.com
--
Thomas Munro
http://www.
On Fri, Sep 15, 2017 at 4:34 PM, Thomas Munro
<thomas.mu...@enterprisedb.com> wrote:
> Here's a version that just forward declares SharedRecordTypmodRegistry
> in session.h (but keeps the typedef in typcache.h where it is useful
> for shorter function prototypes). Neither GCC 6
"utils/typcache.h"
/*
* A struct encapsulating some elements of a user's session. For now this
--
Thomas Munro
http://www.enterprisedb.com
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers
On Fri, Sep 15, 2017 at 3:45 PM, Tom Lane <t...@sss.pgh.pa.us> wrote:
> Thomas Munro <thomas.mu...@enterprisedb.com> writes:
>> My compiler, C++ and more recent C standards are OK with identical
>> redefinition of a typedef like that, but not the older standards or
&g
y getting rid of the code that accesses shmem in the detach hook.
With this patch applied installcheck survives on a cluster with
force_parallel_worker=regress.
--
Thomas Munro
http://www.enterprisedb.com
0001-Fix-crash-in-shared_record_typmod_registry_worker_de.patch
Description: Binary data
--
ed, 40 insertions(+), 8 deletions(-)
I spotted a typo: s/unexpcted/unexpected/.
--
Thomas Munro
http://www.enterprisedb.com
typo.patch
Description: Binary data
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers
control but we can't see its output,
maybe due to -Otarget, before the whole job is nuked by Travis for not
making progress).
--
Thomas Munro
http://www.enterprisedb.com
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers
between different sessions (since reused
backends might as well benefit from prewarmed caches where it makes
sense). For example, if plpgsql is holding onto RECORD TupleDescs or
typmods it would need to stop doing that when it receives a
session-going-away callback, or store its state in some data s
itted
anything in the meantime. Hah. I guess Coverity analysis is going to
have to remain post-commit only.
[1] https://scan.coverity.com/travis_ci
--
Thomas Munro
http://www.enterprisedb.com
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make chan
On Sat, Sep 9, 2017 at 10:23 AM, Thomas Munro
<thomas.mu...@enterprisedb.com> wrote:
> On Sat, Sep 9, 2017 at 9:49 AM, Tom Lane <t...@sss.pgh.pa.us> wrote:
>> Robert Haas <rh...@postgresql.org> writes:
>>> Allow a partitioned table to have a default part
und_whole_row)
elog(ERROR, "unexpected whole-row reference found in partition key");
--
Thomas Munro
http://www.enterprisedb.com
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers
18 matches
Mail list logo
