Fix typo on comment
Author: David Rowley
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/7731c32087faf498db0562cc7e40d256ffc1750f
Modified Files
--
src/backend/utils/adt/json.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On 2017-12-17 11:03:49 -0500, Tom Lane wrote:
> Michael Paquier writes:
> > ... Please note that if you added
> > a volatile cast to "result" as well, then compilation was able to
> > complete and regression tests passed...
>
> Yeah, that squares with my analysis: the problem with the existing te
Fix crashes on plans with multiple Gather (Merge) nodes.
es_query_dsa turns out to be broken by design, because it supposes
that there is only one DSA for the whole query, whereas there is
actually one per Gather (Merge) node. For now, work around that
problem by setting and clearing the pointer
Fix crashes on plans with multiple Gather (Merge) nodes.
es_query_dsa turns out to be broken by design, because it supposes
that there is only one DSA for the whole query, whereas there is
actually one per Gather (Merge) node. For now, work around that
problem by setting and clearing the pointer
Fix bug in cancellation of non-exclusive backup to avoid assertion failure.
Previously an assertion failure occurred when pg_stop_backup() for
non-exclusive backup was aborted while it's waiting for WAL files to
be archived. This assertion failure happened in do_pg_abort_backup()
which was called
Fix bug in cancellation of non-exclusive backup to avoid assertion failure.
Previously an assertion failure occurred when pg_stop_backup() for
non-exclusive backup was aborted while it's waiting for WAL files to
be archived. This assertion failure happened in do_pg_abort_backup()
which was called
Fix bug in cancellation of non-exclusive backup to avoid assertion failure.
Previously an assertion failure occurred when pg_stop_backup() for
non-exclusive backup was aborted while it's waiting for WAL files to
be archived. This assertion failure happened in do_pg_abort_backup()
which was called
doc: Fix figures in example description
oversight in 244c8b466a743d1ec18a7d841bf42669699b3b56
Reported-by: Blaz Merela
Branch
--
REL9_4_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/02f66d8656e8fb1ba56604994149f063c7230a18
Modified Files
--
doc/src/sgml/perfo
doc: Fix figures in example description
oversight in 244c8b466a743d1ec18a7d841bf42669699b3b56
Reported-by: Blaz Merela
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/53cba77b53f98255bfbba9d2612d1a5685feec52
Modified Files
--
doc/src/sgml/perform.sgml
doc: Fix figures in example description
oversight in 244c8b466a743d1ec18a7d841bf42669699b3b56
Reported-by: Blaz Merela
Branch
--
REL9_5_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/195516c9a6d72603969597bb0e495dd269e1ce22
Modified Files
--
doc/src/sgml/perfo
doc: Fix figures in example description
oversight in 244c8b466a743d1ec18a7d841bf42669699b3b56
Reported-by: Blaz Merela
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/db2ee079f54c66f57b5cbfa4c506f73dae9dab1b
Modified Files
--
doc/src/sgml/perfo
doc: Fix figures in example description
oversight in 244c8b466a743d1ec18a7d841bf42669699b3b56
Reported-by: Blaz Merela
Branch
--
REL9_6_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/23b63417e20d548d281cd8f904f6f2ffcebddc8c
Modified Files
--
doc/src/sgml/perfo
Move SCRAM-related name definitions to scram-common.h
Mechanism names for SCRAM and channel binding names have been included
in scram.h by the libpq frontend code, and this header references a set
of routines which are only used by the backend. scram-common.h is on
the contrary usable by both the
Add shared tuplestores.
SharedTuplestore allows multiple participants to write into it and
then read the tuples back from it in parallel. Each reader receives
partial results.
For now it always uses disk files, but other buffering policies and
other kinds of scans (ie each reader receives comple
14 matches
Mail list logo
