Error out on send failure in walsender loop.
I changed the loop in 9.3 to use "goto send_failure" instead of "break" on
errors, but I missed this one case. It was a relatively harmless bug: if
the flush fails once it will most likely fail again as soon as we try to
flush the output again. But it's
Error out on send failure in walsender loop.
I changed the loop in 9.3 to use "goto send_failure" instead of "break" on
errors, but I missed this one case. It was a relatively harmless bug: if
the flush fails once it will most likely fail again as soon as we try to
flush the output again. But it's
Allow VACUUM FULL/CLUSTER to bump freeze horizons even for pg_class.
pg_class is a special case for CLUSTER and VACUUM FULL, so although
commit 3cff1879f8d03cb729368722ca823a4bf74c0cac caused these
operations to advance relfrozenxid and relminmxid for all other
tables, it did not provide the same
Minor corrections to logical decoding patch.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/7e8db2dc420099df3fa73987cf2d2d6d1a609d86
Modified Files
--
src/backend/replication/logical/logical.c |2 +-
src/backend/replication/logical/logicalfuncs.c
Constructors for interval, timestamp, timestamptz
Author: Pavel Stěhule, editorialized somewhat by Álvaro Herrera
Reviewed-by: Tomáš Vondra, Marko Tiikkaja
With input from Fabrízio de Royes Mello, Jim Nasby
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/84df54b22e80
auto_explain: Add logging of trigger execution
Author: Kyotaro HORIGUCHI
Reviewed-by: Jaime Casanova
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/e2a0fc5363e293d29053d0582a1009bc9fef0276
Modified Files
--
contrib/auto_explain/auto_explain.c | 14 +++
Provide a FORCE NULL option to COPY in CSV mode.
This forces an input field containing the quoted null string to be
returned as a NULL. Without this option, only unquoted null strings
behave this way. This helps where some CSV producers insist on quoting
every field, whether or not it is needed. T
On Sun, Mar 2, 2014 at 03:14:35AM +, Stephen Frost wrote:
> Various Coverity-spotted fixes
>
> A number of issues were identified by the Coverity scanner and are
> addressed in this patch. None of these appear to be security issues
> and many are mostly cosmetic changes.
>
> Short comments
K, will check it out. Thanks!
On Tuesday, March 4, 2014, Bruce Momjian wrote:
> On Sun, Mar 2, 2014 at 03:14:35AM +, Stephen Frost wrote:
> > Various Coverity-spotted fixes
> >
> > A number of issues were identified by the Coverity scanner and are
> > addressed in this patch. None of these
Fix whitespace
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/6f37c08057685ee3c6c63222dba0dac012760dde
Modified Files
--
contrib/test_decoding/sql/ddl.sql |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
Sent via pgsql-committers mailing lis
Fix issues with pg_ctl
The new, small, free_readfile managed to have bug in it which could
cause it to try and free something it shouldn't, and fix the case
where it was being called with an invalid pointer leading to a
segfault.
Noted by Bruce, issues introduced and fixed by me.
Branch
--
m
11 matches
Mail list logo