Reset walsender ps title in the main loop
When in streaming mode we can never get out, so it will never
be required, but after a base backup (or other operations)
we can get back to the loop, so the title needs to be cleared.
Branch
--
master
Details
---
Typo fix
Josh Kupershmidt
Branch
--
master
Details
---
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=1c400d330934eb6d70982af522f2bc0458eef48d
Modified Files
--
doc/src/sgml/ref/prepare_transaction.sgml |2 +-
1 files changed, 1 insertions(+), 1
Typo fix
Josh Kupershmidt
Branch
--
REL9_0_STABLE
Details
---
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=a1ed4cf6ca6ee2115d9f618ed7930a97842042a8
Modified Files
--
doc/src/sgml/ref/prepare_transaction.sgml |2 +-
1 files changed, 1 insertions(+), 1
Revert installation of gram.h in 8.3
To make the buildfarm green again, since there is no file to
copy on msvc, and also given discussion about the necessity
of the file at all...
Branch
--
REL8_3_STABLE
Details
---
Tweak create_index_paths()'s test for whether to consider a bitmap scan.
Per my note of a couple days ago, create_index_paths would refuse to
consider any path at all for GIN indexes if the selectivity estimate came
out as 1.0; not even if you tried to force it with enable_seqscan. While
this
Adjust basebackup.c to suppress compiler warnings.
Some versions of gcc complain about variable `tablespaces' might be
clobbered by `longjmp' or `vfork' with the original coding. Fix by
moving the PG_TRY block into a separate subroutine.
Branch
--
master
Details
---
On Tue, Jan 11, 2011 at 19:42, Tom Lane t...@sss.pgh.pa.us wrote:
Adjust basebackup.c to suppress compiler warnings.
Some versions of gcc complain about variable `tablespaces' might be
clobbered by `longjmp' or `vfork' with the original coding. Fix by
moving the PG_TRY block into a separate
Magnus Hagander mag...@hagander.net writes:
On Tue, Jan 11, 2011 at 19:42, Tom Lane t...@sss.pgh.pa.us wrote:
Some versions of gcc complain about variable `tablespaces' might be
clobbered by `longjmp' or `vfork' with the original coding. Fix by
moving the PG_TRY block into a separate
Magnus Hagander mag...@hagander.net writes:
I noticed you didn't create a function prototype at the top of the
file for this function. Was that intentional, or missed? If it was
intentional, can you give me a quick lesson in when it should be done
and whe nit shouldn't? :-)
I think
Add missing function prototype, for consistency
Branch
--
master
Details
---
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=47a5f3e9dab68f47ebadc759afb97b900c437c54
Modified Files
--
src/backend/replication/basebackup.c |1 +
1 files changed, 1
Track walsender state in shared memory and expose in pg_stat_replication
Branch
--
master
Details
---
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=4c8e20f815cbdf043d6d27906fd85ae50c9e4870
Modified Files
--
doc/src/sgml/monitoring.sgml |4 +-
Add some subsection headings
Branch
--
master
Details
---
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=b95ea9dd628a93f564e460b8870228755b520220
Modified Files
--
doc/src/sgml/regress.sgml | 12
1 files changed, 12 insertions(+), 0
Re-add recursive coverage target in src/backend/
This was lost during the recent recursive make change.
Branch
--
master
Details
---
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=e3094fd3a8052bb600b287c5dd844b3b0ac2fe11
Modified Files
--
Unbreak regression tests, apparently broken by commit 4c8e20f
Branch
--
master
Details
---
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=b7a0b42641e764a1e4abc39cc4311b5c779f5955
Modified Files
--
src/test/regress/expected/rules.out |2 +-
1 files
14 matches
Mail list logo