[COMMITTERS] pgsql: Clarify that COPY FREEZE is not a hard rule.
Clarify that COPY FREEZE is not a hard rule. Remove message when FREEZE not honoured, clarify reasons in comments and docs. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/1eb6cee499d19fc9204e059ba37fc2dac32e2f25 Modified Files -- doc/src/sgml/ref/copy.sgml |8 +--- src/backend/commands/copy.c | 10 +- 2 files changed, 10 insertions(+), 8 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Optimize COPY FREEZE with CREATE TABLE also.
Optimize COPY FREEZE with CREATE TABLE also. Jeff Davis, additional test by me Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/1f023f929702efc9fd4230267b0f0e8d72ba5067 Modified Files -- src/backend/commands/copy.c |3 ++- src/test/regress/expected/copy2.out | 12 ++-- src/test/regress/sql/copy2.sql |8 +++- 3 files changed, 19 insertions(+), 4 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Correct xmax test for COPY FREEZE
Correct xmax test for COPY FREEZE Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/ef754fb51b8a40c3b3dc0f3cc42f62eff77649db Modified Files -- src/test/regress/expected/copy2.out | 10 +- 1 files changed, 5 insertions(+), 5 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
Re: [COMMITTERS] pgsql: Correct xmax test for COPY FREEZE
On 7 December 2012 14:19, Simon Riggs wrote: > Correct xmax test for COPY FREEZE It seems I have a script problem at the root cause of this error. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Improve pg_upgrade's status display
Improve pg_upgrade's status display Pg_upgrade displays file names during copy and database names during dump/restore. Andrew Dunstan identified three bugs: * long file names were being truncated to 60 _leading_ characters, which often do not change for long file names * file names were truncated to 60 characters in log files * carriage returns were being output to log files This commit fixes these --- it prints 60 _trailing_ characters to the status display, and full path names without carriage returns to log files. It also suppresses status output to the log file unless verbose mode is used. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/6dd9584507199a6222ff2d6a40028bba69c9175e Modified Files -- contrib/pg_upgrade/dump.c|2 +- contrib/pg_upgrade/pg_upgrade.c |2 +- contrib/pg_upgrade/pg_upgrade.h |4 +- contrib/pg_upgrade/relfilenode.c |2 +- contrib/pg_upgrade/util.c| 40 +++-- 5 files changed, 30 insertions(+), 20 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
