From 8b70eab9fda0bb8e159c7c1fcc12ff5789b674a7 Mon Sep 17 00:00:00 2001 From: "Jonathan S. Katz" Date: Mon, 25 Jun 2018 07:40:25 -0400 Subject: [PATCH] Updates to 11 Beta 1 announcement --- releases/11/beta/11beta1.md | 4 ++-- releases/11/beta/11beta1.txt | 5 ++--- 2 files changed, 4 insertions(+), 5 deletions(-) diff --git a/releases/11/beta/11beta1.md b/releases/11/beta/11beta1.md index 997395c..4f51751 100644 --- a/releases/11/beta/11beta1.md +++ b/releases/11/beta/11beta1.md @@ -55,7 +55,7 @@ The PostgreSQL Global Development Group recognizes that while PostgreSQL itself Prior to PostgreSQL 11, one such feature was using the `ALTER TABLE .. ADD COLUMN` command where the newly created column had a `DEFAULT` value that was not NULL. Prior to PostgreSQL 11, when executing aforementioned statement, PostgreSQL would rewrite the whole table, which on larger tables in active systems could cause a cascade of problems. PostgreSQL 11 removes the need to rewrite the table in most cases, and as such running `ALTER TABLE .. ADD COLUMN .. DEFAULT ..` will execute extremely quickly. -Another feature that fell into this category was the inability to intuitively quit from the PostgreSQL command-line (`psql`). There has been numerous recorded complaints of users trying to quit with the `quit` and `exit` commands, only to learn that the command to do so was `\q` (or _Ctrl-D_ if someone was so inclined). +Another feature that fell into this category was the inability to intuitively quit from the PostgreSQL command-line (`psql`). There has been numerous recorded complaints of users trying to quit with the `quit` and `exit` commands, only to learn that the command to do so was `\q`. We have heard your frustrations and have now added the ability to quit the command-line using the keywords `quit` and `exit` and hope that quitting a PostgreSQL session is now as enjoyable as using PostgreSQL. @@ -83,6 +83,6 @@ Links * [Download](https://www.postgresql.org/download/) * [Beta Testing Information](https://www.postgresql.org/developer/beta/) -* [PostgreSQL 11 Beta Release Notes](https://www.postgresql.org/docs/devel/static/release-11.html) +* [PostgreSQL 11 Beta Release Notes](https://www.postgresql.org/docs/11/static/release-11.html) * [PostgreSQL 11 Open Issues](https://wiki.postgresql.org/wiki/PostgreSQL_11_Open_Items) * [Submit a Bug](https://www.postgresql.org/account/submitbug/) diff --git a/releases/11/beta/11beta1.txt b/releases/11/beta/11beta1.txt index 8875175..0fbdf4f 100644 --- a/releases/11/beta/11beta1.txt +++ b/releases/11/beta/11beta1.txt @@ -97,8 +97,7 @@ removes the need to rewrite the table in most cases, and as such running Another feature that fell into this category was the inability to intuitively quit from the PostgreSQL command-line (`psql`). There has been numerous recorded complaints of users trying to quit with the `quit` and `exit` commands, only to -learn that the command to do so was `\q` (or _Ctrl-D_ if someone was so -inclined). +learn that the command to do so was `\q`. We have heard your frustrations and have now added the ability to quit the command-line using the keywords `quit` and `exit` and hope that quitting a @@ -141,6 +140,6 @@ Links * Download: https://www.postgresql.org/download/ * Beta Testing Information: https://www.postgresql.org/developer/beta/ -* PostgreSQL 11 Beta Release Notes: https://www.postgresql.org/docs/devel/static/release-11.html +* PostgreSQL 11 Beta Release Notes: https://www.postgresql.org/docs/11/static/release-11.html * PostgreSQL 11 Open Issues: https://wiki.postgresql.org/wiki/PostgreSQL_11_Open_Items * Submit a Bug: https://www.postgresql.org/account/submitbug/ -- 2.39.5