[COMMITTERS] pgsql: Replace references to COLLATE "en_CA" with COLLATE "POSIX".

2016-12-07 Thread Robert Haas
Replace references to COLLATE "en_CA" with COLLATE "POSIX". Another attmempt to fix the tests which were added by commit f0e44751d7175fa3394da2c8f85e3ceb3cdbfe63. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/cd5d3af44e2a4f73c692d4653941c0516f967cb7 Modified Files

[COMMITTERS] pgsql: Replace references to COLLATE "en_US" with COLLATE "C".

2016-12-07 Thread Robert Haas
Replace references to COLLATE "en_US" with COLLATE "C". Commit f0e44751d7175fa3394da2c8f85e3ceb3cdbfe63 is turning the buildfarm red; let's try something hopefully more portable. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/71efd34fb8047e3e4fdfc9d6900b7affd20a0235

[COMMITTERS] pgsql: Implement table partitioning.

2016-12-07 Thread Robert Haas
Implement table partitioning. Table partitioning is like table inheritance and reuses much of the existing infrastructure, but there are some important differences. The parent is called a partitioned table and is always empty; it may not have indexes or non-inherited constraints, since those make

[COMMITTERS] pgsql: Restore psql's SIGPIPE setting if popen() fails.

2016-12-07 Thread Tom Lane
Restore psql's SIGPIPE setting if popen() fails. Ancient oversight in PageOutput(): if popen() fails, we'd better reset the SIGPIPE handler before returning stdout, because ClosePager() won't. Noticed while fixing the empty-PAGER issue. Branch -- master Details --- http://git.postgresql.

[COMMITTERS] pgsql: Restore psql's SIGPIPE setting if popen() fails.

2016-12-07 Thread Tom Lane
Restore psql's SIGPIPE setting if popen() fails. Ancient oversight in PageOutput(): if popen() fails, we'd better reset the SIGPIPE handler before returning stdout, because ClosePager() won't. Noticed while fixing the empty-PAGER issue. Branch -- REL9_4_STABLE Details --- http://git.post

[COMMITTERS] pgsql: Restore psql's SIGPIPE setting if popen() fails.

2016-12-07 Thread Tom Lane
Restore psql's SIGPIPE setting if popen() fails. Ancient oversight in PageOutput(): if popen() fails, we'd better reset the SIGPIPE handler before returning stdout, because ClosePager() won't. Noticed while fixing the empty-PAGER issue. Branch -- REL9_5_STABLE Details --- http://git.post

[COMMITTERS] pgsql: Restore psql's SIGPIPE setting if popen() fails.

2016-12-07 Thread Tom Lane
Restore psql's SIGPIPE setting if popen() fails. Ancient oversight in PageOutput(): if popen() fails, we'd better reset the SIGPIPE handler before returning stdout, because ClosePager() won't. Noticed while fixing the empty-PAGER issue. Branch -- REL9_2_STABLE Details --- http://git.post

[COMMITTERS] pgsql: Restore psql's SIGPIPE setting if popen() fails.

2016-12-07 Thread Tom Lane
Restore psql's SIGPIPE setting if popen() fails. Ancient oversight in PageOutput(): if popen() fails, we'd better reset the SIGPIPE handler before returning stdout, because ClosePager() won't. Noticed while fixing the empty-PAGER issue. Branch -- REL9_3_STABLE Details --- http://git.post

[COMMITTERS] pgsql: Restore psql's SIGPIPE setting if popen() fails.

2016-12-07 Thread Tom Lane
Restore psql's SIGPIPE setting if popen() fails. Ancient oversight in PageOutput(): if popen() fails, we'd better reset the SIGPIPE handler before returning stdout, because ClosePager() won't. Noticed while fixing the empty-PAGER issue. Branch -- REL9_6_STABLE Details --- http://git.post

[COMMITTERS] pgsql: Handle empty or all-blank PAGER setting more sanely in psql.

2016-12-07 Thread Tom Lane
Handle empty or all-blank PAGER setting more sanely in psql. If the PAGER environment variable is set but contains an empty string, psql would pass it to "sh" which would silently exit, causing whatever query output we were printing to vanish entirely. This is quite mystifying; it took a long tim

[COMMITTERS] pgsql: Handle empty or all-blank PAGER setting more sanely in psql.

2016-12-07 Thread Tom Lane
Handle empty or all-blank PAGER setting more sanely in psql. If the PAGER environment variable is set but contains an empty string, psql would pass it to "sh" which would silently exit, causing whatever query output we were printing to vanish entirely. This is quite mystifying; it took a long tim

[COMMITTERS] pgsql: Handle empty or all-blank PAGER setting more sanely in psql.

2016-12-07 Thread Tom Lane
Handle empty or all-blank PAGER setting more sanely in psql. If the PAGER environment variable is set but contains an empty string, psql would pass it to "sh" which would silently exit, causing whatever query output we were printing to vanish entirely. This is quite mystifying; it took a long tim

[COMMITTERS] pgsql: Handle empty or all-blank PAGER setting more sanely in psql.

2016-12-07 Thread Tom Lane
Handle empty or all-blank PAGER setting more sanely in psql. If the PAGER environment variable is set but contains an empty string, psql would pass it to "sh" which would silently exit, causing whatever query output we were printing to vanish entirely. This is quite mystifying; it took a long tim

[COMMITTERS] pgsql: Handle empty or all-blank PAGER setting more sanely in psql.

2016-12-07 Thread Tom Lane
Handle empty or all-blank PAGER setting more sanely in psql. If the PAGER environment variable is set but contains an empty string, psql would pass it to "sh" which would silently exit, causing whatever query output we were printing to vanish entirely. This is quite mystifying; it took a long tim

[COMMITTERS] pgsql: Handle empty or all-blank PAGER setting more sanely in psql.

2016-12-07 Thread Tom Lane
Handle empty or all-blank PAGER setting more sanely in psql. If the PAGER environment variable is set but contains an empty string, psql would pass it to "sh" which would silently exit, causing whatever query output we were printing to vanish entirely. This is quite mystifying; it took a long tim