Modify create_index regression test to avoid intermittent failures.
We have been seeing intermittent buildfarm failures due to a query
sometimes not using an index-only scan plan, because a background
auto-ANALYZE prevented the table's all-visible bits from being set
immediately, thereby causing t
Fix planner's handling of RETURNING lists in writable CTEs.
setrefs.c failed to do "rtoffset" adjustment of Vars in RETURNING lists,
which meant they were left with the wrong varnos when the RETURNING list
was in a subquery. That was never possible before writable CTEs, of
course, but now it's br
Fix planner's handling of RETURNING lists in writable CTEs.
setrefs.c failed to do "rtoffset" adjustment of Vars in RETURNING lists,
which meant they were left with the wrong varnos when the RETURNING list
was in a subquery. That was never possible before writable CTEs, of
course, but now it's br
Fix edge-case behavior of pg_next_dst_boundary().
Due to rather sloppy thinking (on my part, I'm afraid) about the
appropriate behavior for boundary conditions, pg_next_dst_boundary() gave
undefined, platform-dependent results when the input time is exactly the
last recorded DST transition time fo
Fix edge-case behavior of pg_next_dst_boundary().
Due to rather sloppy thinking (on my part, I'm afraid) about the
appropriate behavior for boundary conditions, pg_next_dst_boundary() gave
undefined, platform-dependent results when the input time is exactly the
last recorded DST transition time fo
Fix edge-case behavior of pg_next_dst_boundary().
Due to rather sloppy thinking (on my part, I'm afraid) about the
appropriate behavior for boundary conditions, pg_next_dst_boundary() gave
undefined, platform-dependent results when the input time is exactly the
last recorded DST transition time fo
Fix edge-case behavior of pg_next_dst_boundary().
Due to rather sloppy thinking (on my part, I'm afraid) about the
appropriate behavior for boundary conditions, pg_next_dst_boundary() gave
undefined, platform-dependent results when the input time is exactly the
last recorded DST transition time fo
Fix edge-case behavior of pg_next_dst_boundary().
Due to rather sloppy thinking (on my part, I'm afraid) about the
appropriate behavior for boundary conditions, pg_next_dst_boundary() gave
undefined, platform-dependent results when the input time is exactly the
last recorded DST transition time fo
Remove prototype for nonexistent function.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/ca1e1a8da11d188df738ba67632c0805a00d3f27
Modified Files
--
src/include/storage/standby.h |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
--
Sent via pg
Another trivial comment-typo fix.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/9873001e6d1177d543a2e46273e738d726670f1f
Modified Files
--
src/backend/access/common/reloptions.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
--
Sent via
PL/Python: Improve error messages
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/65ca8e68b7b21de7641d8ec9b7d4b9a2dd5e081d
Modified Files
--
src/pl/plpython/plpy_plpymodule.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
--
Sent via pgsq
PL/Python: Improve error messages
Branch
--
REL9_1_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/f33f1a875f9b799da202408e118a47e4ee2bab7b
Modified Files
--
src/pl/plpython/plpython.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
--
Sent via pgsq
12 matches
Mail list logo