doc: Add serial comma
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/f15b820a5c60b10f3ac1b2fdb37d534ecb0a4bf8
Modified Files
--
doc/src/sgml/ref/psql-ref.sgml |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
Sent via pgsql-committers mailing
psql: Improve spelling
Branch
--
REL9_5_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/28bfdc581a552e2a3b1f0faded352188559e5aca
Modified Files
--
src/bin/psql/command.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
--
Sent via pgsql-co
doc: Fix markup and improve placeholder names
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/9ff1a11a2d9797f5d48fc1994faa40f738ba9b7e
Modified Files
--
doc/src/sgml/ref/insert.sgml | 28 ++--
1 file changed, 14 insertions(+), 14
doc: Fix markup and improve placeholder names
Branch
--
REL9_5_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/0638a62dec88b148b560e5fb240087098fe58887
Modified Files
--
doc/src/sgml/ref/insert.sgml | 28 ++--
1 file changed, 14 insertions(
psql: Improve spelling
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/77a7bb3da2479833c200a96b028fbfbe4312a201
Modified Files
--
src/bin/psql/command.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
--
Sent via pgsql-committer
Clean up some psql issues around handling of the query output file.
Formerly, if "psql -o foo" failed to open the output file "foo", it would
print an error message but then carry on as though -o had not been
specified at all. This seems contrary to expectation: a program that
cannot open its out
Clean up some psql issues around handling of the query output file.
Formerly, if "psql -o foo" failed to open the output file "foo", it would
print an error message but then carry on as though -o had not been
specified at all. This seems contrary to expectation: a program that
cannot open its out
Further tweak commit_timestamp behavior
As pointed out by Fujii Masao, we weren't quite there on a standby
behaving sanely: first because we were failing to acquire the correct
state in the case where no XLOG_PARAMETER_CHANGE message was sent
(because a checkpoint had already happened after the se
Further tweak commit_timestamp behavior
As pointed out by Fujii Masao, we weren't quite there on a standby
behaving sanely: first because we were failing to acquire the correct
state in the case where no XLOG_PARAMETER_CHANGE message was sent
(because a checkpoint had already happened after the se
