[COMMITTERS] pgsql: Remove duplicated words in comments.

Remove duplicated words in comments. David Rowley Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/a10589a5128e841d3faf94a2d8417a4f5497c4ac Modified Files -- src/backend/replication/walsender.c |6 +++--- src/backend/utils/adt/array_userfuncs.c |

[COMMITTERS] pgsql: Remove duplicated words in comments.

Remove duplicated words in comments. David Rowley Branch -- REL9_4_STABLE Details --- http://git.postgresql.org/pg/commitdiff/131fb7fc66332b4c13cab2f1a5a87aab0767ebd9 Modified Files -- src/backend/replication/walsender.c |6 +++--- src/bin/pg_basebackup/pg_basebackup.c

[COMMITTERS] pgsql: Remove duplicated words in comments.

Remove duplicated words in comments. David Rowley Branch -- REL9_2_STABLE Details --- http://git.postgresql.org/pg/commitdiff/3a9951d62e37d0660505d9e6fe6647f6b4743008 Modified Files -- src/bin/pg_basebackup/pg_basebackup.c |2 +- 1 file changed, 1 insertion(+), 1 deletion

[COMMITTERS] pgsql: Remove duplicated words in comments.

Remove duplicated words in comments. David Rowley Branch -- REL9_3_STABLE Details --- http://git.postgresql.org/pg/commitdiff/8dfddf14c598d389b8c95d402de529298274b94f Modified Files -- src/backend/replication/walsender.c |6 +++--- src/bin/pg_basebackup/pg_basebackup.c

Re: [COMMITTERS] pgsql: Fix multiple bugs and infelicities in pg_rewind.

On Mon, Mar 30, 2015 at 9:02 AM, Tom Lane wrote: > Fix multiple bugs and infelicities in pg_rewind. > > Bugs all spotted by Coverity, including wrong realloc() size request > and memory leaks. Cosmetic improvements by me. > > The usage of the global variable "filemap" here is still pretty awful,

[COMMITTERS] pgsql: Add system view pg_stat_ssl

Add system view pg_stat_ssl This view shows information about all connections, such as if the connection is using SSL, which cipher is used, and which client certificate (if any) is used. Reviews by Alex Shulgin, Heikki Linnakangas, Andres Freund & Michael Paquier Branch -- master Details -

[COMMITTERS] pgsql: Free leaked result set in pg_rewind

Free leaked result set in pg_rewind It was not significant in practice, it was just one instance of a small result set, but let's pacify Coverity. Michael Paquier Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/74a68e37d059295e97cc55683c9342912a0ec81f Modified File

Re: [COMMITTERS] pgsql: Fix multiple bugs and infelicities in pg_rewind.

On 04/12/2015 11:46 AM, Michael Paquier wrote: On Mon, Mar 30, 2015 at 9:02 AM, Tom Lane wrote: Fix multiple bugs and infelicities in pg_rewind. Bugs all spotted by Coverity, including wrong realloc() size request and memory leaks. Cosmetic improvements by me. The usage of the global variabl

[COMMITTERS] pgsql: emacs: Set indent-tabs-mode in perl-mode

emacs: Set indent-tabs-mode in perl-mode This matches existing practice, but makes the setup complete and consistent with the C code setup. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/442663f133f1caec51919402463e6e31362baee3 Modified Files -- .dir-lo

[COMMITTERS] pgsql: Silence gettext warning about '\r' escape sequence in translatab

Silence gettext warning about '\r' escape sequence in translatable string. gettext was unhappy about the commit b216ad7 because it revealed the problem that internationalized messages may contain '\r' escape sequence in pg_rewind. This commit moves '\r' to a separate printf() call. Michael Paquie

Re: [COMMITTERS] pgsql: Mark the second argument of pg_log as the translatable string in

On Sun, Apr 12, 2015 at 3:03 PM, Michael Paquier wrote: > On Sun, Apr 12, 2015 at 10:17 AM, Alvaro Herrera wrote: >> What pg_basebackup's progress_report() does is have the message in the >> translatable part not include the \r; the \r is in a separate fprintf() >> call. > > Like the attached then