[COMMITTERS] pgsql: Use in pg_upgrade's procedure

2015-09-01 Thread Alvaro Herrera
Use in pg_upgrade's procedure For clarity, so that the substeps are not numbered identically to the outer procedure's steps. Per report from Andy Colson in http://www.postgresql.org/message-id/[email protected] Branch -- master Details --- http://git.postgresql.org/pg/co

[COMMITTERS] pgsql: Use in pg_upgrade's procedure

2015-09-01 Thread Alvaro Herrera
Use in pg_upgrade's procedure For clarity, so that the substeps are not numbered identically to the outer procedure's steps. Per report from Andy Colson in http://www.postgresql.org/message-id/[email protected] Branch -- REL9_5_STABLE Details --- http://git.postgresql.or

[COMMITTERS] pgsql: Allow notifications to bgworkers without database connections.

2015-09-01 Thread Robert Haas
Allow notifications to bgworkers without database connections. Previously, if one background worker registered another background worker and set bgw_notify_pid while for the second background worker, it would not receive notifications from the postmaster unless, at the time the "parent" was regist

[COMMITTERS] pgsql: Allow notifications to bgworkers without database connections.

2015-09-01 Thread Robert Haas
Allow notifications to bgworkers without database connections. Previously, if one background worker registered another background worker and set bgw_notify_pid while for the second background worker, it would not receive notifications from the postmaster unless, at the time the "parent" was regist

[COMMITTERS] pgsql: pg_upgrade docs: clarify rsync and move verification step

2015-09-01 Thread Bruce Momjian
pg_upgrade docs: clarify rsync and move verification step These are adjustments based on someone using the new standby upgrade steps. Report by Andy Colson Backpatch through 9.5 Branch -- REL9_5_STABLE Details --- http://git.postgresql.org/pg/commitdiff/813e08123bd9eb7d7eb7bc6eac43b74

[COMMITTERS] pgsql: pg_upgrade docs: clarify rsync and move verification step

2015-09-01 Thread Bruce Momjian
pg_upgrade docs: clarify rsync and move verification step These are adjustments based on someone using the new standby upgrade steps. Report by Andy Colson Backpatch through 9.5 Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/46bd95e2a873feb4799b77eca7276cf758e36c

[COMMITTERS] pgsql: Flush to show results of TestLib.pm (TAP) test as we go.

2015-09-01 Thread Kevin Grittner
Flush to show results of TestLib.pm (TAP) test as we go. It appears that some attempt was made to do this using autocommit, but it wasn't effective (at least on Ubuntu 14.04). Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/adb495049f575563930f3c1fbef2843bda3ae46d M

Re: [COMMITTERS] pgsql: Flush to show results of TestLib.pm (TAP) test as we go.

2015-09-01 Thread Tom Lane
Kevin Grittner writes: > Flush to show results of TestLib.pm (TAP) test as we go. Probably would be reasonable to back-patch that. SimpleTee.pm is currently identical in all branches that have it, and I see no good reason to let it diverge. Our need for intelligible test output is not any weake

[COMMITTERS] pgsql: Document that PL/Python now returns floats using repr() not str(

2015-09-01 Thread Tom Lane
Document that PL/Python now returns floats using repr() not str(). Commit 1ce7a57ca neglected to update the user-facing documentation, which described the old behavior precisely. Branch -- REL9_5_STABLE Details --- http://git.postgresql.org/pg/commitdiff/e2e78acccaa94e7d64dc2bc0b124cfcf2

[COMMITTERS] pgsql: Document that PL/Python now returns floats using repr() not str(

2015-09-01 Thread Tom Lane
Document that PL/Python now returns floats using repr() not str(). Commit 1ce7a57ca neglected to update the user-facing documentation, which described the old behavior precisely. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/075ab425bdbb4bb2de41624305f20885cae7ba7e