Postgres Changelog - All Versions

Below is a complete, one-page listing of changes across all Postgres versions. All versions of PostgreSQL 12 and older are EOL (end of life) and unsupported.
This page was generated on May 08, 2025 by a script (version 1.39) by Greg Sabino Mullane, and contains information for 533 versions of Postgres.

Postgres 17
(end of life: Nov 8, 2029)

17.5 (2025-05-08)
17.4 (2025-02-20)
17.3 (2025-02-13)
17.2 (2024-11-21)
17.1 (2024-11-14)
17.0 (2024-09-26)
Postgres 16
(end of life: Nov 9, 2028)

16.9 (2025-05-08)
16.8 (2025-02-20)
16.7 (2025-02-13)
16.6 (2024-11-21)
16.5 (2024-11-14)
16.4 (2024-08-08)
16.3 (2024-05-09)
16.2 (2024-02-08)
16.1 (2023-11-09)
16.0 (2023-09-14)
Postgres 15
(end of life: Nov 11, 2027)

15.13 (2025-05-08)
15.12 (2025-02-20)
15.11 (2025-02-13)
15.10 (2024-11-21)
15.9 (2024-11-14)
15.8 (2024-08-08)
15.7 (2024-05-09)
15.6 (2024-02-08)
15.5 (2023-11-09)
15.4 (2023-08-10)
15.3 (2023-05-11)
15.2 (2023-02-09)
15.1 (2022-11-10)
15.0 (2022-10-13)
Postgres 14
(end of life: Nov 12, 2026)

14.18 (2025-05-08)
14.17 (2025-02-20)
14.16 (2025-02-13)
14.15 (2024-11-21)
14.14 (2024-11-14)
14.13 (2024-08-08)
14.12 (2024-05-09)
14.11 (2024-02-08)
14.10 (2023-11-09)
14.9 (2023-08-10)
14.8 (2023-05-11)
14.7 (2023-02-09)
14.6 (2022-11-10)
14.5 (2022-08-11)
14.4 (2022-06-16)
14.3 (2022-05-12)
14.2 (2022-02-10)
14.1 (2021-11-11)
14.0 (2021-09-30)
Postgres 13
(end of life: Nov 13, 2025)

13.21 (2025-05-08)
13.20 (2025-02-20)
13.19 (2025-02-13)
13.18 (2024-11-21)
13.17 (2024-11-14)
13.16 (2024-08-08)
13.15 (2024-05-09)
13.14 (2024-02-08)
13.13 (2023-11-09)
13.12 (2023-08-10)
13.11 (2023-05-11)
13.10 (2023-02-09)
13.9 (2022-11-10)
13.8 (2022-08-11)
13.7 (2022-05-12)
13.6 (2022-02-10)
13.5 (2021-11-11)
13.4 (2021-08-12)
13.3 (2021-05-13)
13.2 (2021-02-11)
13.1 (2020-11-12)
13.0 (2020-09-24)
Postgres 12
(end of life: Nov 14, 2024)

12.22 (2024-11-21)
12.21 (2024-11-14)
12.20 (2024-08-08)
12.19 (2024-05-09)
12.18 (2024-02-08)
12.17 (2023-11-09)
12.16 (2023-08-10)
12.15 (2023-05-11)
12.14 (2023-02-09)
12.13 (2022-11-10)
12.12 (2022-08-11)
12.11 (2022-05-12)
12.10 (2022-02-10)
12.9 (2021-11-11)
12.8 (2021-08-12)
12.7 (2021-05-13)
12.6 (2021-02-11)
12.5 (2020-11-12)
12.4 (2020-08-13)
12.3 (2020-05-14)
12.2 (2020-02-13)
12.1 (2019-11-14)
12.0 (2019-10-03)
Postgres 11
(end of life: Nov 9, 2023)

11.22 (2023-11-09)
11.21 (2023-08-10)
11.20 (2023-05-11)
11.19 (2023-02-09)
11.18 (2022-11-10)
11.17 (2022-08-11)
11.16 (2022-05-12)
11.15 (2022-02-10)
11.14 (2021-11-11)
11.13 (2021-08-12)
11.12 (2021-05-13)
11.11 (2021-02-11)
11.10 (2020-11-12)
11.9 (2020-08-13)
11.8 (2020-05-14)
11.7 (2020-02-13)
11.6 (2019-11-14)
11.5 (2019-08-08)
11.4 (2019-06-20)
11.3 (2019-05-09)
11.2 (2019-02-14)
11.1 (2018-11-08)
11.0 (2018-10-18)
Postgres 10
(end of life: Nov 10, 2022)

10.23 (2022-11-10)
10.22 (2022-08-11)
10.21 (2022-05-12)
10.20 (2022-02-10)
10.19 (2021-11-11)
10.18 (2021-08-12)
10.17 (2021-05-13)
10.16 (2021-02-11)
10.15 (2020-11-12)
10.14 (2020-08-13)
10.13 (2020-05-14)
10.12 (2020-02-13)
10.11 (2019-11-14)
10.10 (2019-08-08)
10.9 (2019-06-20)
10.8 (2019-05-09)
10.7 (2019-02-14)
10.6 (2018-11-08)
10.5 (2018-08-09)
10.4 (2018-05-10)
10.3 (2018-03-01)
10.2 (2018-02-08)
10.1 (2017-11-09)
10.0 (2017-10-05)
Postgres 9.6
(end of life: Nov 11, 2021)

9.6.24 (2021-11-11)
9.6.23 (2021-08-12)
9.6.22 (2021-05-13)
9.6.21 (2021-02-11)
9.6.20 (2020-11-12)
9.6.19 (2020-08-13)
9.6.18 (2020-05-14)
9.6.17 (2020-02-13)
9.6.16 (2019-11-14)
9.6.15 (2019-08-08)
9.6.14 (2019-06-20)
9.6.13 (2019-05-09)
9.6.12 (2019-02-14)
9.6.11 (2018-11-08)
9.6.10 (2018-08-09)
9.6.9 (2018-05-10)
9.6.8 (2018-03-01)
9.6.7 (2018-02-08)
9.6.6 (2017-11-09)
9.6.5 (2017-08-31)
9.6.4 (2017-08-10)
9.6.3 (2017-05-11)
9.6.2 (2017-02-09)
9.6.1 (2016-10-27)
9.6.0 (2016-09-29)
Postgres 9.5
(end of life: Feb 11, 2021)

9.5.25 (2021-02-11)
9.5.24 (2020-11-12)
9.5.23 (2020-08-13)
9.5.22 (2020-05-14)
9.5.21 (2020-02-13)
9.5.20 (2019-11-14)
9.5.19 (2019-08-08)
9.5.18 (2019-06-20)
9.5.17 (2019-05-09)
9.5.16 (2019-02-14)
9.5.15 (2018-11-08)
9.5.14 (2018-08-09)
9.5.13 (2018-05-10)
9.5.12 (2018-03-01)
9.5.11 (2018-02-08)
9.5.10 (2017-11-09)
9.5.9 (2017-08-31)
9.5.8 (2017-08-10)
9.5.7 (2017-05-11)
9.5.6 (2017-02-09)
9.5.5 (2016-10-27)
9.5.4 (2016-08-11)
9.5.3 (2016-05-12)
9.5.2 (2016-03-31)
9.5.1 (2016-02-11)
9.5.0 (2016-01-07)
Postgres 9.4
(end of life: Feb 13, 2020)

9.4.26 (2020-02-13)
9.4.25 (2019-11-14)
9.4.24 (2019-08-08)
9.4.23 (2019-06-20)
9.4.22 (2019-05-09)
9.4.21 (2019-02-14)
9.4.20 (2018-11-08)
9.4.19 (2018-08-09)
9.4.18 (2018-05-10)
9.4.17 (2018-03-01)
9.4.16 (2018-02-08)
9.4.15 (2017-11-09)
9.4.14 (2017-08-31)
9.4.13 (2017-08-10)
9.4.12 (2017-05-11)
9.4.11 (2017-02-09)
9.4.10 (2016-10-27)
9.4.9 (2016-08-11)
9.4.8 (2016-05-12)
9.4.7 (2016-03-31)
9.4.6 (2016-02-11)
9.4.5 (2015-10-08)
9.4.4 (2015-06-12)
9.4.3 (2015-06-04)
9.4.2 (2015-05-22)
9.4.1 (2015-02-05)
9.4.0 (2014-12-18)
Postgres 9.3
(end of life: Nov 8, 2018)

9.3.25 (2018-11-08)
9.3.24 (2018-08-09)
9.3.23 (2018-05-10)
9.3.22 (2018-03-01)
9.3.21 (2018-02-08)
9.3.20 (2017-11-09)
9.3.19 (2017-08-31)
9.3.18 (2017-08-10)
9.3.17 (2017-05-11)
9.3.16 (2017-02-09)
9.3.15 (2016-10-27)
9.3.14 (2016-08-11)
9.3.13 (2016-05-12)
9.3.12 (2016-03-31)
9.3.11 (2016-02-11)
9.3.10 (2015-10-08)
9.3.9 (2015-06-12)
9.3.8 (2015-06-04)
9.3.7 (2015-05-22)
9.3.6 (2015-02-05)
9.3.5 (2014-07-24)
9.3.4 (2014-03-20)
9.3.3 (2014-02-20)
9.3.2 (2013-12-05)
9.3.1 (2013-10-10)
9.3.0 (2013-09-09)
Postgres 9.2
(end of life: Nov 9, 2017)

9.2.24 (2017-11-09)
9.2.23 (2017-08-31)
9.2.22 (2017-08-10)
9.2.21 (2017-05-11)
9.2.20 (2017-02-09)
9.2.19 (2016-10-27)
9.2.18 (2016-08-11)
9.2.17 (2016-05-12)
9.2.16 (2016-03-31)
9.2.15 (2016-02-11)
9.2.14 (2015-10-08)
9.2.13 (2015-06-12)
9.2.12 (2015-06-04)
9.2.11 (2015-05-22)
9.2.10 (2015-02-05)
9.2.9 (2014-07-24)
9.2.8 (2014-03-20)
9.2.7 (2014-02-20)
9.2.6 (2013-12-05)
9.2.5 (2013-10-10)
9.2.4 (2013-04-04)
9.2.3 (2013-02-07)
9.2.2 (2012-12-06)
9.2.1 (2012-09-24)
9.2.0 (2012-09-10)
Postgres 9.1
(end of life: Oct 27, 2016)

9.1.24 (2016-10-27)
9.1.23 (2016-08-11)
9.1.22 (2016-05-12)
9.1.21 (2016-03-31)
9.1.20 (2016-02-11)
9.1.19 (2015-10-08)
9.1.18 (2015-06-12)
9.1.17 (2015-06-04)
9.1.16 (2015-05-22)
9.1.15 (2015-02-05)
9.1.14 (2014-07-24)
9.1.13 (2014-03-20)
9.1.12 (2014-02-20)
9.1.11 (2013-12-05)
9.1.10 (2013-10-10)
9.1.9 (2013-04-04)
9.1.8 (2013-02-07)
9.1.7 (2012-12-06)
9.1.6 (2012-09-24)
9.1.5 (2012-08-17)
9.1.4 (2012-06-04)
9.1.3 (2012-02-27)
9.1.2 (2011-12-05)
9.1.1 (2011-09-26)
9.1.0 (2011-09-12)
Postgres 9.0
(end of life: Oct 8, 2015)

9.0.23 (2015-10-08)
9.0.22 (2015-06-12)
9.0.21 (2015-06-04)
9.0.20 (2015-05-22)
9.0.19 (2015-02-05)
9.0.18 (2014-07-24)
9.0.17 (2014-03-20)
9.0.16 (2014-02-20)
9.0.15 (2013-12-05)
9.0.14 (2013-10-10)
9.0.13 (2013-04-04)
9.0.12 (2013-02-07)
9.0.11 (2012-12-06)
9.0.10 (2012-09-24)
9.0.9 (2012-08-17)
9.0.8 (2012-06-04)
9.0.7 (2012-02-27)
9.0.6 (2011-12-05)
9.0.5 (2011-09-26)
9.0.4 (2011-04-18)
9.0.3 (2011-01-31)
9.0.2 (2010-12-16)
9.0.1 (2010-10-04)
9.0.0 (2010-09-20)
Postgres 8.4
(end of life: Jul 24, 2014)

8.4.22 (2014-07-24)
8.4.21 (2014-03-20)
8.4.20 (2014-02-20)
8.4.19 (2013-12-05)
8.4.18 (2013-10-10)
8.4.17 (2013-04-04)
8.4.16 (2013-02-07)
8.4.15 (2012-12-06)
8.4.14 (2012-09-24)
8.4.13 (2012-08-17)
8.4.12 (2012-06-04)
8.4.11 (2012-02-27)
8.4.10 (2011-12-05)
8.4.9 (2011-09-26)
8.4.8 (2011-04-18)
8.4.7 (2011-01-31)
8.4.6 (2010-12-16)
8.4.5 (2010-10-04)
8.4.4 (2010-05-17)
8.4.3 (2010-03-15)
8.4.2 (2009-12-14)
8.4.1 (2009-09-09)
8.4.0 (2009-07-01)
Postgres 8.3
(end of life: Feb 7, 2013)

8.3.23 (2013-02-07)
8.3.22 (2012-12-06)
8.3.21 (2012-09-24)
8.3.20 (2012-08-17)
8.3.19 (2012-06-04)
8.3.18 (2012-02-27)
8.3.17 (2011-12-05)
8.3.16 (2011-09-26)
8.3.15 (2011-04-18)
8.3.14 (2011-01-31)
8.3.13 (2010-12-16)
8.3.12 (2010-10-04)
8.3.11 (2010-05-17)
8.3.10 (2010-03-15)
8.3.9 (2009-12-14)
8.3.8 (2009-09-09)
8.3.7 (2009-03-16)
8.3.6 (2009-02-02)
8.3.5 (2008-11-03)
8.3.4 (2008-09-22)
8.3.3 (2008-06-12)
8.3.2 (never released!)
8.3.1 (2008-03-17)
8.3.0 (2008-02-04)
Postgres 8.2
(end of life: Dec 5, 2011)

8.2.23 (2011-12-05)
8.2.22 (2011-09-26)
8.2.21 (2011-04-18)
8.2.20 (2011-01-31)
8.2.19 (2010-12-16)
8.2.18 (2010-10-04)
8.2.17 (2010-05-17)
8.2.16 (2010-03-15)
8.2.15 (2009-12-14)
8.2.14 (2009-09-09)
8.2.13 (2009-03-16)
8.2.12 (2009-02-02)
8.2.11 (2008-11-03)
8.2.10 (2008-09-22)
8.2.9 (2008-06-12)
8.2.8 (never released!)
8.2.7 (2008-03-17)
8.2.6 (2008-01-07)
8.2.5 (2007-09-17)
8.2.4 (2007-04-23)
8.2.3 (2007-02-07)
8.2.2 (2007-02-05)
8.2.1 (2007-01-08)
8.2.0 (2006-12-05)
Postgres 8.1
(end of life: Nov 8, 2010)

8.1.23 (2010-12-16)
8.1.22 (2010-10-04)
8.1.21 (2010-05-17)
8.1.20 (2010-03-15)
8.1.19 (2009-12-14)
8.1.18 (2009-09-09)
8.1.17 (2009-03-16)
8.1.16 (2009-02-02)
8.1.15 (2008-11-03)
8.1.14 (2008-09-22)
8.1.13 (2008-06-12)
8.1.12 (never released!)
8.1.11 (2008-01-07)
8.1.10 (2007-09-17)
8.1.9 (2007-04-23)
8.1.8 (2007-02-07)
8.1.7 (2007-02-05)
8.1.6 (2007-01-08)
8.1.5 (2006-10-16)
8.1.4 (2006-05-23)
8.1.3 (2006-02-14)
8.1.2 (2006-01-09)
8.1.1 (2005-12-12)
8.1.0 (2005-11-08)
Postgres 8.0
(end of life: Oct 1, 2010)

8.0.26 (2010-10-04)
8.0.25 (2010-05-17)
8.0.24 (2010-03-15)
8.0.23 (2009-12-14)
8.0.22 (2009-09-09)
8.0.21 (2009-03-16)
8.0.20 (2009-02-02)
8.0.19 (2008-11-03)
8.0.18 (2008-09-22)
8.0.17 (2008-06-12)
8.0.16 (never released!)
8.0.15 (2008-01-07)
8.0.14 (2007-09-17)
8.0.13 (2007-04-23)
8.0.12 (2007-02-07)
8.0.11 (2007-02-05)
8.0.10 (2007-01-08)
8.0.9 (2006-10-16)
8.0.8 (2006-05-23)
8.0.7 (2006-02-14)
8.0.6 (2006-01-09)
8.0.5 (2005-12-12)
8.0.4 (2005-10-04)
8.0.3 (2005-05-09)
8.0.2 (2005-04-07)
8.0.1 (2005-01-31)
8.0.0 (2005-01-19)
Postgres 7.4
(end of life: Oct 1, 2010)

7.4.30 (2010-10-04)
7.4.29 (2010-05-17)
7.4.28 (2010-03-15)
7.4.27 (2009-12-14)
7.4.26 (2009-09-09)
7.4.25 (2009-03-16)
7.4.24 (2009-02-02)
7.4.23 (2008-11-03)
7.4.22 (2008-09-22)
7.4.21 (2008-06-12)
7.4.20 (never released!)
7.4.19 (2008-01-07)
7.4.18 (2007-09-17)
7.4.17 (2007-04-23)
7.4.16 (2007-02-05)
7.4.15 (2007-01-08)
7.4.14 (2006-10-16)
7.4.13 (2006-05-23)
7.4.12 (2006-02-14)
7.4.11 (2006-01-09)
7.4.10 (2005-12-12)
7.4.9 (2005-10-04)
7.4.8 (2005-05-09)
7.4.7 (2005-01-31)
7.4.6 (2004-10-22)
7.4.5 (2004-08-18)
7.4.4 (2004-08-16)
7.4.3 (2004-06-14)
7.4.2 (2004-03-08)
7.4.1 (2003-12-22)
7.4.0 (2003-11-17)
Postgres 7.3
(end of life: Nov 27, 2007)

7.3.21 (2008-01-07)
7.3.20 (2007-09-17)
7.3.19 (2007-04-23)
7.3.18 (2007-02-05)
7.3.17 (2007-01-08)
7.3.16 (2006-10-16)
7.3.15 (2006-05-23)
7.3.14 (2006-02-14)
7.3.13 (2006-01-09)
7.3.12 (2005-12-12)
7.3.11 (2005-10-04)
7.3.10 (2005-05-09)
7.3.9 (2005-01-31)
7.3.8 (2004-10-22)
7.3.7 (2004-08-16)
7.3.6 (2004-03-02)
7.3.5 (2003-12-03)
7.3.4 (2003-07-24)
7.3.3 (2003-05-22)
7.3.2 (2003-02-04)
7.3.1 (2002-12-18)
7.3.0 (2002-11-27)
Postgres 7.2
(end of life: Feb 4, 2007)

7.2.8 (2005-05-09)
7.2.7 (2005-01-31)
7.2.6 (2004-10-22)
7.2.5 (2004-08-16)
7.2.4 (2003-01-30)
7.2.3 (2002-10-01)
7.2.2 (2002-08-23)
7.2.1 (2002-03-21)
7.2.0 (2002-02-04)

Postgres 7.1
(end of life: Apr 13, 2006)

7.1.3 (2001-08-15)
7.1.2 (2001-05-11)
7.1.1 (2001-05-05)
7.1.0 (2001-04-13)

Postgres 7.0
(end of life: May 8, 2005)

7.0.3 (2000-11-11)
7.0.2 (2000-06-05)
7.0.1 (2000-06-01)
7.0.0 (2000-05-08)
Postgres 6.5
(end of life: Jun 9, 2004)

6.5.3 (1999-10-13)
6.5.2 (1999-09-15)
6.5.1 (1999-07-15)
6.5.0 (1999-06-09)

Postgres 6.4
(end of life: Oct 30, 2003)

6.4.2 (1998-12-20)
6.4.1 (1998-12-18)
6.4.0 (1998-10-30)

Postgres 6.3
(end of life: Mar 1, 2003)

6.3.2 (1998-04-07)
6.3.1 (1998-03-23)
6.3.0 (1998-03-01)

Postgres 6.2
(end of life)

6.2.1 (1997-10-17)
6.2.0 (1997-10-02)

Postgres 6.1
(end of life)

6.1.1 (1997-07-22)
6.1.0 (1997-06-08)

Postgres 6.0 and earlier...
(end of life)

6.0.0 (1997-01-29)
1.09 (1996-11-04)
1.02 (1996-08-01)
1.01 (1996-02-23)
1.0 (1995-09-05)
0.03 (1995-07-21)
0.02 (1995-05-25)
0.01 (1995-05-01)

Postgres version 17.5

Release date: 2025-05-08

This release contains a variety of fixes from 17.4. For information about new features in major release 17, see Version 17.0.

 Migration to Version 17.5

A dump/restore is not required for those running 17.X.

However, if you have any self-referential foreign key constraints on partitioned tables, it may be necessary to recreate those constraints to ensure that they are being enforced correctly. See the second changelog entry below.

Also, if you have any BRIN bloom indexes, it may be advisable to reindex them after updating. See the third changelog entry below.

Also, if you are upgrading from a version earlier than 17.1, see Version 17.1.

 Changes

Postgres version 17.4

Release date: 2025-02-20

This release contains a few fixes from 17.3. For information about new features in major release 17, see Version 17.0.

 Migration to Version 17.4

A dump/restore is not required for those running 17.X.

However, if you are upgrading from a version earlier than 17.1, see Version 17.1.

 Changes

Postgres version 17.3

Release date: 2025-02-13

This release contains a variety of fixes from 17.2. For information about new features in major release 17, see Version 17.0.

 Migration to Version 17.3

A dump/restore is not required for those running 17.X.

However, if you are upgrading from a version earlier than 17.1, see Version 17.1.

 Changes

Postgres version 17.2

Release date: 2024-11-21

This release contains a few fixes from 17.1. For information about new features in major release 17, see Version 17.0.

 Migration to Version 17.2

A dump/restore is not required for those running 17.X.

However, if you are upgrading from a version earlier than 17.1, see Version 17.1.

 Changes

Postgres version 17.1

Release date: 2024-11-14

This release contains a variety of fixes from 17.0. For information about new features in major release 17, see Version 17.0.

 Migration to Version 17.1

A dump/restore is not required for those running 17.X.

However, if you have ever detached a partition from a partitioned table that has a foreign-key reference to another partitioned table, and not dropped the former partition, then you may have catalog and/or data corruption to repair, as detailed in the fifth changelog entry below.

Also, in the uncommon case that a database's LC_CTYPE setting is C while its LC_COLLATE setting is some other locale, indexes on textual columns should be reindexed, as described in the sixth changelog entry below.

 Changes

Postgres version 17.0

Release date: 2024-09-26

 Overview

PostgreSQL 17 contains many new features and enhancements, including:

The above items and other new features of PostgreSQL 17 are explained in more detail in the sections below.

 Migration to Version 17

A dump/restore using pg_dumpall or use of pg_upgrade or logical replication is required for those wishing to migrate data from any previous release. See Section 18.6 for general information on migrating to new major releases.

Version 17 contains a number of changes that may affect compatibility with previous releases. Observe the following incompatibilities:

 Changes

Below you will find a detailed account of the changes between PostgreSQL 17 and the previous major release.

 Server (PG 17.0)

 Optimizer (PG 17.0)

 Indexes (PG 17.0)

 General Performance (PG 17.0)

 Monitoring (PG 17.0)

 Privileges (PG 17.0)

 Server Configuration (PG 17.0)

 Streaming Replication and Recovery (PG 17.0)

 Logical Replication (PG 17.0)

 Utility Commands (PG 17.0)

 EXPLAIN (PG 17.0)

 Data Types (PG 17.0)

 MERGE (PG 17.0)

 Functions (PG 17.0)

 PL/pgSQL (PG 17.0)

 libpq (PG 17.0)

 psql (PG 17.0)

 Server Applications (PG 17.0)

 Source Code (PG 17.0)

 Additional Modules (PG 17.0)

 pg_stat_statements (PG 17.0)

 Acknowledgments

The following individuals (in alphabetical order) have contributed to this release as patch authors, committers, reviewers, testers, or reporters of issues.

Postgres version 16.9

Release date: 2025-05-08

This release contains a variety of fixes from 16.8. For information about new features in major release 16, see Version 16.0.

 Migration to Version 16.9

A dump/restore is not required for those running 16.X.

However, if you have any self-referential foreign key constraints on partitioned tables, it may be necessary to recreate those constraints to ensure that they are being enforced correctly. See the second changelog entry below.

Also, if you have any BRIN bloom indexes, it may be advisable to reindex them after updating. See the third changelog entry below.

Also, if you are upgrading from a version earlier than 16.5, see Version 16.5.

 Changes

Postgres version 16.8

Release date: 2025-02-20

This release contains a few fixes from 16.7. For information about new features in major release 16, see Version 16.0.

 Migration to Version 16.8

A dump/restore is not required for those running 16.X.

However, if you are upgrading from a version earlier than 16.5, see Version 16.5.

 Changes

Postgres version 16.7

Release date: 2025-02-13

This release contains a variety of fixes from 16.6. For information about new features in major release 16, see Version 16.0.

 Migration to Version 16.7

A dump/restore is not required for those running 16.X.

However, if you are upgrading from a version earlier than 16.5, see Version 16.5.

 Changes

Postgres version 16.6

Release date: 2024-11-21

This release contains a few fixes from 16.5. For information about new features in major release 16, see Version 16.0.

 Migration to Version 16.6

A dump/restore is not required for those running 16.X.

However, if you are upgrading from a version earlier than 16.5, see Version 16.5.

 Changes

Postgres version 16.5

Release date: 2024-11-14

This release contains a variety of fixes from 16.4. For information about new features in major release 16, see Version 16.0.

 Migration to Version 16.5

A dump/restore is not required for those running 16.X.

However, if you have ever detached a partition from a partitioned table that has a foreign-key reference to another partitioned table, and not dropped the former partition, then you may have catalog and/or data corruption to repair, as detailed in the fifth changelog entry below.

Also, if you are upgrading from a version earlier than 16.3, see Version 16.3.

 Changes

Postgres version 16.4

Release date: 2024-08-08

This release contains a variety of fixes from 16.3. For information about new features in major release 16, see Version 16.0.

 Migration to Version 16.4

A dump/restore is not required for those running 16.X.

However, if you are upgrading from a version earlier than 16.3, see Version 16.3.

 Changes

Postgres version 16.3

Release date: 2024-05-09

This release contains a variety of fixes from 16.2. For information about new features in major release 16, see Version 16.0.

 Migration to Version 16.3

A dump/restore is not required for those running 16.X.

However, a security vulnerability was found in the system views pg_stats_ext and pg_stats_ext_exprs, potentially allowing authenticated database users to see data they shouldn't. If this is of concern in your installation, follow the steps in the first changelog entry below to rectify it.

Also, if you are upgrading from a version earlier than 16.2, see Version 16.2.

 Changes

Postgres version 16.2

Release date: 2024-02-08

This release contains a variety of fixes from 16.1. For information about new features in major release 16, see Version 16.0.

 Migration to Version 16.2

A dump/restore is not required for those running 16.X.

However, one bug was fixed that could have resulted in corruption of GIN indexes during concurrent updates. If you suspect such corruption, reindex affected indexes after installing this update.

Also, if you are upgrading from a version earlier than 16.1, see Version 16.1.

 Changes

Postgres version 16.1

Release date: 2023-11-09

This release contains a variety of fixes from 16.0. For information about new features in major release 16, see Version 16.0.

 Migration to Version 16.1

A dump/restore is not required for those running 16.X.

However, several mistakes have been discovered that could lead to certain types of indexes yielding wrong search results or being unnecessarily inefficient. It is advisable to REINDEX potentially-affected indexes after installing this update. See the fourth through seventh changelog entries below.

 Changes

Postgres version 16.0

Release date: 2023-09-14

 Overview

PostgreSQL 16 contains many new features and enhancements, including:

The above items and other new features of PostgreSQL 16 are explained in more detail in the sections below.

 Migration to Version 16

A dump/restore using pg_dumpall or use of pg_upgrade or logical replication is required for those wishing to migrate data from any previous release. See Section 19.6 for general information on migrating to new major releases.

Version 16 contains a number of changes that may affect compatibility with previous releases. Observe the following incompatibilities:

 Changes

Below you will find a detailed account of the changes between PostgreSQL 16 and the previous major release.

 Server (PG 16.0)

 Optimizer (PG 16.0)

 General Performance (PG 16.0)

 Monitoring (PG 16.0)

 Privileges (PG 16.0)

 Server Configuration (PG 16.0)

 pg_hba.conf (PG 16.0)

 Localization (PG 16.0)

 Logical Replication (PG 16.0)

 Utility Commands (PG 16.0)

 Data Types (PG 16.0)

 General Queries (PG 16.0)

 Functions (PG 16.0)

 PL/pgSQL (PG 16.0)

 libpq (PG 16.0)

 Client Applications (PG 16.0)

 psql (PG 16.0)

 pg_dump (PG 16.0)

 Server Applications (PG 16.0)

 Source Code (PG 16.0)

 Additional Modules (PG 16.0)

 postgres_fdw (PG 16.0)

 Acknowledgments

The following individuals (in alphabetical order) have contributed to this release as patch authors, committers, reviewers, testers, or reporters of issues.

Postgres version 15.13

Release date: 2025-05-08

This release contains a variety of fixes from 15.12. For information about new features in major release 15, see Version 15.0.

 Migration to Version 15.13

A dump/restore is not required for those running 15.X.

However, if you have any self-referential foreign key constraints on partitioned tables, it may be necessary to recreate those constraints to ensure that they are being enforced correctly. See the second changelog entry below.

Also, if you have any BRIN bloom indexes, it may be advisable to reindex them after updating. See the third changelog entry below.

Also, if you are upgrading from a version earlier than 15.9, see Version 15.9.

 Changes

Postgres version 15.12

Release date: 2025-02-20

This release contains a few fixes from 15.11. For information about new features in major release 15, see Version 15.0.

 Migration to Version 15.12

A dump/restore is not required for those running 15.X.

However, if you are upgrading from a version earlier than 15.9, see Version 15.9.

 Changes

Postgres version 15.11

Release date: 2025-02-13

This release contains a variety of fixes from 15.10. For information about new features in major release 15, see Version 15.0.

 Migration to Version 15.11

A dump/restore is not required for those running 15.X.

However, if you are upgrading from a version earlier than 15.9, see Version 15.9.

 Changes

Postgres version 15.10

Release date: 2024-11-21

This release contains a few fixes from 15.9. For information about new features in major release 15, see Version 15.0.

 Migration to Version 15.10

A dump/restore is not required for those running 15.X.

However, if you are upgrading from a version earlier than 15.9, see Version 15.9.

 Changes

Postgres version 15.9

Release date: 2024-11-14

This release contains a variety of fixes from 15.8. For information about new features in major release 15, see Version 15.0.

 Migration to Version 15.9

A dump/restore is not required for those running 15.X.

However, if you have ever detached a partition from a partitioned table that has a foreign-key reference to another partitioned table, and not dropped the former partition, then you may have catalog and/or data corruption to repair, as detailed in the fifth changelog entry below.

Also, if you are upgrading from a version earlier than 15.7, see Version 15.7.

 Changes

Postgres version 15.8

Release date: 2024-08-08

This release contains a variety of fixes from 15.7. For information about new features in major release 15, see Version 15.0.

 Migration to Version 15.8

A dump/restore is not required for those running 15.X.

However, if you are upgrading from a version earlier than 15.7, see Version 15.7.

 Changes

Postgres version 15.7

Release date: 2024-05-09

This release contains a variety of fixes from 15.6. For information about new features in major release 15, see Version 15.0.

 Migration to Version 15.7

A dump/restore is not required for those running 15.X.

However, a security vulnerability was found in the system views pg_stats_ext and pg_stats_ext_exprs, potentially allowing authenticated database users to see data they shouldn't. If this is of concern in your installation, follow the steps in the first changelog entry below to rectify it.

Also, if you are upgrading from a version earlier than 15.6, see Version 15.6.

 Changes

Postgres version 15.6

Release date: 2024-02-08

This release contains a variety of fixes from 15.5. For information about new features in major release 15, see Version 15.0.

 Migration to Version 15.6

A dump/restore is not required for those running 15.X.

However, one bug was fixed that could have resulted in corruption of GIN indexes during concurrent updates. If you suspect such corruption, reindex affected indexes after installing this update.

Also, if you are upgrading from a version earlier than 15.5, see Version 15.5.

 Changes

Postgres version 15.5

Release date: 2023-11-09

This release contains a variety of fixes from 15.4. For information about new features in major release 15, see Version 15.0.

 Migration to Version 15.5

A dump/restore is not required for those running 15.X.

However, several mistakes have been discovered that could lead to certain types of indexes yielding wrong search results or being unnecessarily inefficient. It is advisable to REINDEX potentially-affected indexes after installing this update. See the fourth through seventh changelog entries below.

Also, if you are upgrading from a version earlier than 15.4, see Version 15.4.

 Changes

Postgres version 15.4

Release date: 2023-08-10

This release contains a variety of fixes from 15.3. For information about new features in major release 15, see Version 15.0.

 Migration to Version 15.4

A dump/restore is not required for those running 15.X.

However, if you use BRIN indexes, it may be advisable to reindex them; see the third changelog entry below.

Also, if you are upgrading from a version earlier than 15.1, see Version 15.1.

 Changes

Postgres version 15.3

Release date: 2023-05-11

This release contains a variety of fixes from 15.2. For information about new features in major release 15, see Version 15.0.

 Migration to Version 15.3

A dump/restore is not required for those running 15.X.

However, if you are upgrading from a version earlier than 15.1, see Version 15.1.

 Changes

Postgres version 15.2

Release date: 2023-02-09

This release contains a variety of fixes from 15.1. For information about new features in major release 15, see Version 15.0.

 Migration to Version 15.2

A dump/restore is not required for those running 15.X.

However, if you are upgrading from a version earlier than 15.1, see Version 15.1.

 Changes

Postgres version 15.1

Release date: 2022-11-10

This release contains a variety of fixes from 15.0. For information about new features in major release 15, see Version 15.0.

 Migration to Version 15.1

A dump/restore is not required for those running 15.X.

However, if you regularly create and drop tables exceeding 1GB, see the first changelog entry below.

 Changes

Postgres version 15.0

Release date: 2022-10-13

 Overview

PostgreSQL 15 contains many new features and enhancements, including:

The above items and other new features of PostgreSQL 15 are explained in more detail in the sections below.

 Migration to Version 15

A dump/restore using pg_dumpall or use of pg_upgrade or logical replication is required for those wishing to migrate data from any previous release. See Section 19.6 for general information on migrating to new major releases.

Version 15 contains a number of changes that may affect compatibility with previous releases. Observe the following incompatibilities:

 Changes

Below you will find a detailed account of the changes between PostgreSQL 15 and the previous major release.

 Server (PG 15.0)

 Partitioning (PG 15.0)

 Indexes (PG 15.0)

 Optimizer (PG 15.0)

 General Performance (PG 15.0)

 Monitoring (PG 15.0)

 Privileges (PG 15.0)

 Server Configuration (PG 15.0)

 Streaming Replication and Recovery (PG 15.0)

 Logical Replication (PG 15.0)

 Utility Commands (PG 15.0)

 Data Types (PG 15.0)

 Functions (PG 15.0)

 PL/pgSQL (PG 15.0)

 libpq (PG 15.0)

 Client Applications (PG 15.0)

 psql (PG 15.0)

 pg_dump (PG 15.0)

 Server Applications (PG 15.0)

 pg_upgrade (PG 15.0)

 pg_waldump (PG 15.0)

 Documentation (PG 15.0)

 Source Code (PG 15.0)

 Additional Modules (PG 15.0)

 postgres_fdw (PG 15.0)

 Acknowledgments

The following individuals (in alphabetical order) have contributed to this release as patch authors, committers, reviewers, testers, or reporters of issues.

Postgres version 14.18

Release date: 2025-05-08

This release contains a variety of fixes from 14.17. For information about new features in major release 14, see Version 14.0.

 Migration to Version 14.18

A dump/restore is not required for those running 14.X.

However, if you have any self-referential foreign key constraints on partitioned tables, it may be necessary to recreate those constraints to ensure that they are being enforced correctly. See the second changelog entry below.

Also, if you have any BRIN bloom indexes, it may be advisable to reindex them after updating. See the third changelog entry below.

Also, if you are upgrading from a version earlier than 14.14, see Version 14.14.

 Changes

Postgres version 14.17

Release date: 2025-02-20

This release contains a few fixes from 14.16. For information about new features in major release 14, see Version 14.0.

 Migration to Version 14.17

A dump/restore is not required for those running 14.X.

However, if you are upgrading from a version earlier than 14.14, see Version 14.14.

 Changes

Postgres version 14.16

Release date: 2025-02-13

This release contains a variety of fixes from 14.15. For information about new features in major release 14, see Version 14.0.

 Migration to Version 14.16

A dump/restore is not required for those running 14.X.

However, if you are upgrading from a version earlier than 14.14, see Version 14.14.

 Changes

Postgres version 14.15

Release date: 2024-11-21

This release contains a few fixes from 14.14. For information about new features in major release 14, see Version 14.0.

 Migration to Version 14.15

A dump/restore is not required for those running 14.X.

However, if you are upgrading from a version earlier than 14.14, see Version 14.14.

 Changes

Postgres version 14.14

Release date: 2024-11-14

This release contains a variety of fixes from 14.13. For information about new features in major release 14, see Version 14.0.

 Migration to Version 14.14

A dump/restore is not required for those running 14.X.

However, if you have ever detached a partition from a partitioned table that has a foreign-key reference to another partitioned table, and not dropped the former partition, then you may have catalog and/or data corruption to repair, as detailed in the fifth changelog entry below.

Also, if you are upgrading from a version earlier than 14.12, see Version 14.12.

 Changes

Postgres version 14.13

Release date: 2024-08-08

This release contains a variety of fixes from 14.12. For information about new features in major release 14, see Version 14.0.

 Migration to Version 14.13

A dump/restore is not required for those running 14.X.

However, if you are upgrading from a version earlier than 14.12, see Version 14.12.

 Changes

Postgres version 14.12

Release date: 2024-05-09

This release contains a variety of fixes from 14.11. For information about new features in major release 14, see Version 14.0.

 Migration to Version 14.12

A dump/restore is not required for those running 14.X.

However, a security vulnerability was found in the system views pg_stats_ext and pg_stats_ext_exprs, potentially allowing authenticated database users to see data they shouldn't. If this is of concern in your installation, follow the steps in the first changelog entry below to rectify it.

Also, if you are upgrading from a version earlier than 14.11, see Version 14.11.

 Changes

Postgres version 14.11

Release date: 2024-02-08

This release contains a variety of fixes from 14.10. For information about new features in major release 14, see Version 14.0.

 Migration to Version 14.11

A dump/restore is not required for those running 14.X.

However, one bug was fixed that could have resulted in corruption of GIN indexes during concurrent updates. If you suspect such corruption, reindex affected indexes after installing this update.

Also, if you are upgrading from a version earlier than 14.10, see Version 14.10.

 Changes

Postgres version 14.10

Release date: 2023-11-09

This release contains a variety of fixes from 14.9. For information about new features in major release 14, see Version 14.0.

 Migration to Version 14.10

A dump/restore is not required for those running 14.X.

However, several mistakes have been discovered that could lead to certain types of indexes yielding wrong search results or being unnecessarily inefficient. It is advisable to REINDEX potentially-affected indexes after installing this update. See the fourth through seventh changelog entries below.

Also, if you are upgrading from a version earlier than 14.9, see Version 14.9.

 Changes

Postgres version 14.9

Release date: 2023-08-10

This release contains a variety of fixes from 14.8. For information about new features in major release 14, see Version 14.0.

 Migration to Version 14.9

A dump/restore is not required for those running 14.X.

However, if you use BRIN indexes, it may be advisable to reindex them; see the second changelog entry below.

Also, if you are upgrading from a version earlier than 14.4, see Version 14.4.

 Changes

Postgres version 14.8

Release date: 2023-05-11

This release contains a variety of fixes from 14.7. For information about new features in major release 14, see Version 14.0.

 Migration to Version 14.8

A dump/restore is not required for those running 14.X.

However, if you are upgrading from a version earlier than 14.4, see Version 14.4.

 Changes

Postgres version 14.7

Release date: 2023-02-09

This release contains a variety of fixes from 14.6. For information about new features in major release 14, see Version 14.0.

 Migration to Version 14.7

A dump/restore is not required for those running 14.X.

However, if you are upgrading from a version earlier than 14.4, see Version 14.4.

 Changes

Postgres version 14.6

Release date: 2022-11-10

This release contains a variety of fixes from 14.5. For information about new features in major release 14, see Version 14.0.

 Migration to Version 14.6

A dump/restore is not required for those running 14.X.

However, if you are upgrading from a version earlier than 14.4, see Version 14.4.

 Changes

Postgres version 14.5

Release date: 2022-08-11

This release contains a variety of fixes from 14.4. For information about new features in major release 14, see Version 14.0.

 Migration to Version 14.5

A dump/restore is not required for those running 14.X.

However, if you are upgrading from a version earlier than 14.4, see Version 14.4.

 Changes

Postgres version 14.4

Release date: 2022-06-16

This release contains a variety of fixes from 14.3. For information about new features in major release 14, see Version 14.0.

 Migration to Version 14.4

A dump/restore is not required for those running 14.X.

However, if you have any indexes that were created using the CONCURRENTLY option under 14.X, you should re-index them after updating. See the first changelog entry below.

Also, if you are upgrading from a version earlier than 14.3, see Version 14.3.

 Changes

Postgres version 14.3

Release date: 2022-05-12

This release contains a variety of fixes from 14.2. For information about new features in major release 14, see Version 14.0.

 Migration to Version 14.3

A dump/restore is not required for those running 14.X.

However, if you have any GiST indexes on columns of type ltree (supplied by the contrib/ltree extension), you should re-index them after updating. See the second changelog entry below.

Also, if you are upgrading from a version earlier than 14.2, see Version 14.2.

 Changes

Postgres version 14.2

Release date: 2022-02-10

This release contains a variety of fixes from 14.1. For information about new features in major release 14, see Version 14.0.

 Migration to Version 14.2

A dump/restore is not required for those running 14.X.

However, some bugs have been found that may have resulted in corrupted indexes, as explained in the first two changelog entries. If any of those cases apply to you, it's recommended to reindex possibly-affected indexes after updating.

Also, if you are upgrading from a version earlier than 14.1, see Version 14.1.

 Changes

Postgres version 14.1

Release date: 2021-11-11

This release contains a variety of fixes from 14.0. For information about new features in major release 14, see Version 14.0.

 Migration to Version 14.1

A dump/restore is not required for those running 14.X.

However, note that installations using physical replication should update standby servers before the primary server, as explained in the third changelog entry below.

Also, several bugs have been found that may have resulted in corrupted indexes, as explained in the next several changelog entries. If any of those cases apply to you, it's recommended to reindex possibly-affected indexes after updating.

 Changes

Postgres version 14.0

Release date: 2021-09-30

 Overview

PostgreSQL 14 contains many new features and enhancements, including:

The above items and other new features of PostgreSQL 14 are explained in more detail in the sections below.

 Migration to Version 14

A dump/restore using pg_dumpall or use of pg_upgrade or logical replication is required for those wishing to migrate data from any previous release. See Section 19.6 for general information on migrating to new major releases.

Version 14 contains a number of changes that may affect compatibility with previous releases. Observe the following incompatibilities:

 Changes

Below you will find a detailed account of the changes between PostgreSQL 14 and the previous major release.

 Server (PG 14.0)

 Vacuuming (PG 14.0)

 Partitioning (PG 14.0)

 Indexes (PG 14.0)

 Optimizer (PG 14.0)

 General Performance (PG 14.0)

 Monitoring (PG 14.0)

 System Views (PG 14.0)

 Authentication (PG 14.0)

 Server Configuration (PG 14.0)

 Streaming Replication and Recovery (PG 14.0)

 Logical Replication (PG 14.0)

 SELECT, INSERT (PG 14.0)

 Utility Commands (PG 14.0)

 Data Types (PG 14.0)

 Functions (PG 14.0)

 PL/pgSQL (PG 14.0)

 Client Interfaces (PG 14.0)

 Client Applications (PG 14.0)

 psql (PG 14.0)

 Server Applications (PG 14.0)

 Documentation (PG 14.0)

 Source Code (PG 14.0)

 Additional Modules (PG 14.0)

 pg_stat_statements (PG 14.0)

 postgres_fdw (PG 14.0)

 Acknowledgments

The following individuals (in alphabetical order) have contributed to this release as patch authors, committers, reviewers, testers, or reporters of issues.

Postgres version 13.21

Release date: 2025-05-08

This release contains a variety of fixes from 13.20. For information about new features in major release 13, see Version 13.0.

The PostgreSQL community will stop releasing updates for the 13.X release series in November 2025. Users are encouraged to update to a newer release branch soon.

 Migration to Version 13.21

A dump/restore is not required for those running 13.X.

However, if you have any self-referential foreign key constraints on partitioned tables, it may be necessary to recreate those constraints to ensure that they are being enforced correctly. See the second changelog entry below.

Also, if you are upgrading from a version earlier than 13.17, see Version 13.17.

 Changes

Postgres version 13.20

Release date: 2025-02-20

This release contains a few fixes from 13.19. For information about new features in major release 13, see Version 13.0.

The PostgreSQL community will stop releasing updates for the 13.X release series in November 2025. Users are encouraged to update to a newer release branch soon.

 Migration to Version 13.20

A dump/restore is not required for those running 13.X.

However, if you are upgrading from a version earlier than 13.17, see Version 13.17.

 Changes

Postgres version 13.19

Release date: 2025-02-13

This release contains a variety of fixes from 13.18. For information about new features in major release 13, see Version 13.0.

The PostgreSQL community will stop releasing updates for the 13.X release series in November 2025. Users are encouraged to update to a newer release branch soon.

 Migration to Version 13.19

A dump/restore is not required for those running 13.X.

However, if you are upgrading from a version earlier than 13.17, see Version 13.17.

 Changes

Postgres version 13.18

Release date: 2024-11-21

This release contains a few fixes from 13.17. For information about new features in major release 13, see Version 13.0.

 Migration to Version 13.18

A dump/restore is not required for those running 13.X.

However, if you are upgrading from a version earlier than 13.17, see Version 13.17.

 Changes

Postgres version 13.17

Release date: 2024-11-14

This release contains a variety of fixes from 13.16. For information about new features in major release 13, see Version 13.0.

 Migration to Version 13.17

A dump/restore is not required for those running 13.X.

However, if you have ever detached a partition from a partitioned table that has a foreign-key reference to another partitioned table, and not dropped the former partition, then you may have catalog and/or data corruption to repair, as detailed in the fifth changelog entry below.

Also, if you are upgrading from a version earlier than 13.14, see Version 13.14.

 Changes

Postgres version 13.16

Release date: 2024-08-08

This release contains a variety of fixes from 13.15. For information about new features in major release 13, see Version 13.0.

 Migration to Version 13.16

A dump/restore is not required for those running 13.X.

However, if you are upgrading from a version earlier than 13.14, see Version 13.14.

 Changes

Postgres version 13.15

Release date: 2024-05-09

This release contains a variety of fixes from 13.14. For information about new features in major release 13, see Version 13.0.

 Migration to Version 13.15

A dump/restore is not required for those running 13.X.

However, if you are upgrading from a version earlier than 13.14, see Version 13.14.

 Changes

Postgres version 13.14

Release date: 2024-02-08

This release contains a variety of fixes from 13.13. For information about new features in major release 13, see Version 13.0.

 Migration to Version 13.14

A dump/restore is not required for those running 13.X.

However, one bug was fixed that could have resulted in corruption of GIN indexes during concurrent updates. If you suspect such corruption, reindex affected indexes after installing this update.

Also, if you are upgrading from a version earlier than 13.13, see Version 13.13.

 Changes

Postgres version 13.13

Release date: 2023-11-09

This release contains a variety of fixes from 13.12. For information about new features in major release 13, see Version 13.0.

 Migration to Version 13.13

A dump/restore is not required for those running 13.X.

However, several mistakes have been discovered that could lead to certain types of indexes yielding wrong search results. It is advisable to REINDEX potentially-affected indexes after installing this update. See the fourth and fifth changelog entries below.

Also, if you are upgrading from a version earlier than 13.12, see Version 13.12.

 Changes

Postgres version 13.12

Release date: 2023-08-10

This release contains a variety of fixes from 13.11. For information about new features in major release 13, see Version 13.0.

 Migration to Version 13.12

A dump/restore is not required for those running 13.X.

However, if you use BRIN indexes, it may be advisable to reindex them; see the second changelog entry below.

Also, if you are upgrading from a version earlier than 13.7, see Version 13.7.

 Changes

Postgres version 13.11

Release date: 2023-05-11

This release contains a variety of fixes from 13.10. For information about new features in major release 13, see Version 13.0.

 Migration to Version 13.11

A dump/restore is not required for those running 13.X.

However, if you are upgrading from a version earlier than 13.7, see Version 13.7.

 Changes

Postgres version 13.10

Release date: 2023-02-09

This release contains a variety of fixes from 13.9. For information about new features in major release 13, see Version 13.0.

 Migration to Version 13.10

A dump/restore is not required for those running 13.X.

However, if you are upgrading from a version earlier than 13.7, see Version 13.7.

 Changes

Postgres version 13.9

Release date: 2022-11-10

This release contains a variety of fixes from 13.8. For information about new features in major release 13, see Version 13.0.

 Migration to Version 13.9

A dump/restore is not required for those running 13.X.

However, if you are upgrading from a version earlier than 13.7, see Version 13.7.

 Changes

Postgres version 13.8

Release date: 2022-08-11

This release contains a variety of fixes from 13.7. For information about new features in major release 13, see Version 13.0.

 Migration to Version 13.8

A dump/restore is not required for those running 13.X.

However, if you are upgrading from a version earlier than 13.7, see Version 13.7.

 Changes

Postgres version 13.7

Release date: 2022-05-12

This release contains a variety of fixes from 13.6. For information about new features in major release 13, see Version 13.0.

 Migration to Version 13.7

A dump/restore is not required for those running 13.X.

However, if you have any GiST indexes on columns of type ltree (supplied by the contrib/ltree extension), you should re-index them after updating. See the second changelog entry below.

Also, if you are upgrading from a version earlier than 13.6, see Version 13.6.

 Changes

Postgres version 13.6

Release date: 2022-02-10

This release contains a variety of fixes from 13.5. For information about new features in major release 13, see Version 13.0.

 Migration to Version 13.6

A dump/restore is not required for those running 13.X.

However, if you have applied REINDEX CONCURRENTLY to a TOAST table's index, or observe failures to access TOAST datums, see the first changelog entry below.

Also, if you are upgrading from a version earlier than 13.5, see Version 13.5.

 Changes

Postgres version 13.5

Release date: 2021-11-11

This release contains a variety of fixes from 13.4. For information about new features in major release 13, see Version 13.0.

 Migration to Version 13.5

A dump/restore is not required for those running 13.X.

However, note that installations using physical replication should update standby servers before the primary server, as explained in the third changelog entry below.

Also, several bugs have been found that may have resulted in corrupted indexes, as explained in the next several changelog entries. If any of those cases apply to you, it's recommended to reindex possibly-affected indexes after updating.

Also, if you are upgrading from a version earlier than 13.2, see Version 13.2.

 Changes

Postgres version 13.4

Release date: 2021-08-12

This release contains a variety of fixes from 13.3. For information about new features in major release 13, see Version 13.0.

 Migration to Version 13.4

A dump/restore is not required for those running 13.X.

However, if you are upgrading from a version earlier than 13.2, see Version 13.2.

 Changes

Postgres version 13.3

Release date: 2021-05-13

This release contains a variety of fixes from 13.2. For information about new features in major release 13, see Version 13.0.

 Migration to Version 13.3

A dump/restore is not required for those running 13.X.

However, if you are upgrading from a version earlier than 13.2, see Version 13.2.

 Changes

Postgres version 13.2

Release date: 2021-02-11

This release contains a variety of fixes from 13.1. For information about new features in major release 13, see Version 13.0.

 Migration to Version 13.2

A dump/restore is not required for those running 13.X.

However, see the first changelog item below concerning a possible need to update stored views. Also see the third and fourth changelog items, which describe cases in which reindexing indexes after the upgrade may be advisable.

 Changes

Postgres version 13.1

Release date: 2020-11-12

This release contains a variety of fixes from 13.0. For information about new features in major release 13, see Version 13.0.

 Migration to Version 13.1

A dump/restore is not required for those running 13.X.

 Changes

Postgres version 13.0

Release date: 2020-09-24

 Overview

PostgreSQL 13 contains many new features and enhancements, including:

The above items and other new features of PostgreSQL 13 are explained in more detail in the sections below.

 Migration to Version 13

A dump/restore using pg_dumpall or use of pg_upgrade or logical replication is required for those wishing to migrate data from any previous release. See Section 18.6 for general information on migrating to new major releases.

Version 13 contains a number of changes that may affect compatibility with previous releases. Observe the following incompatibilities:

 Changes

Below you will find a detailed account of the changes between PostgreSQL 13 and the previous major release.

 Server (PG 13.0)

 Partitioning (PG 13.0)

 Indexes (PG 13.0)

 Optimizer (PG 13.0)

 General Performance (PG 13.0)

 Monitoring (PG 13.0)

 System Views (PG 13.0)

 Wait Events (PG 13.0)

 Authentication (PG 13.0)

 Server Configuration (PG 13.0)

 Streaming Replication and Recovery (PG 13.0)

 Utility Commands (PG 13.0)

 Data Types (PG 13.0)

 Functions (PG 13.0)

 PL/pgSQL (PG 13.0)

 Client Interfaces (PG 13.0)

 Client Applications (PG 13.0)

 psql (PG 13.0)

 pgbench (PG 13.0)

 Server Applications (PG 13.0)

 Documentation (PG 13.0)

 Source Code (PG 13.0)

 Additional Modules (PG 13.0)

 Acknowledgments

The following individuals (in alphabetical order) have contributed to this release as patch authors, committers, reviewers, testers, or reporters of issues.

Postgres version 12.22 (end of life as of November 14, 2024)

Release date: 2024-11-21

This release contains a single fix from 12.21. For information about new features in major release 12, see Version 12.0.

This is expected to be the last PostgreSQL release in the 12.X series. Users are encouraged to update to a newer release branch soon.

 Migration to Version 12.22

A dump/restore is not required for those running 12.X.

However, if you are upgrading from a version earlier than 12.18, see Version 12.18.

 Changes

Postgres version 12.21 (end of life as of November 14, 2024)

Release date: 2024-11-14

This release contains a variety of fixes from 12.20. For information about new features in major release 12, see Version 12.0.

This is expected to be the last PostgreSQL release in the 12.X series. Users are encouraged to update to a newer release branch soon.

 Migration to Version 12.21

A dump/restore is not required for those running 12.X.

However, if you are upgrading from a version earlier than 12.18, see Version 12.18.

 Changes

Postgres version 12.20 (end of life as of November 14, 2024)

Release date: 2024-08-08

This release contains a variety of fixes from 12.19. For information about new features in major release 12, see Version 12.0.

The PostgreSQL community will stop releasing updates for the 12.X release series in November 2024. Users are encouraged to update to a newer release branch soon.

 Migration to Version 12.20

A dump/restore is not required for those running 12.X.

However, if you are upgrading from a version earlier than 12.18, see Version 12.18.

 Changes

Postgres version 12.19 (end of life as of November 14, 2024)

Release date: 2024-05-09

This release contains a variety of fixes from 12.18. For information about new features in major release 12, see Version 12.0.

The PostgreSQL community will stop releasing updates for the 12.X release series in November 2024. Users are encouraged to update to a newer release branch soon.

 Migration to Version 12.19

A dump/restore is not required for those running 12.X.

However, if you are upgrading from a version earlier than 12.18, see Version 12.18.

 Changes

Postgres version 12.18 (end of life as of November 14, 2024)

Release date: 2024-02-08

This release contains a variety of fixes from 12.17. For information about new features in major release 12, see Version 12.0.

The PostgreSQL community will stop releasing updates for the 12.X release series in November 2024. Users are encouraged to update to a newer release branch soon.

 Migration to Version 12.18

A dump/restore is not required for those running 12.X.

However, one bug was fixed that could have resulted in corruption of GIN indexes during concurrent updates. If you suspect such corruption, reindex affected indexes after installing this update.

Also, if you are upgrading from a version earlier than 12.17, see Version 12.17.

 Changes

Postgres version 12.17 (end of life as of November 14, 2024)

Release date: 2023-11-09

This release contains a variety of fixes from 12.16. For information about new features in major release 12, see Version 12.0.

 Migration to Version 12.17

A dump/restore is not required for those running 12.X.

However, if you use GiST indexes, it may be advisable to reindex them; see the fourth changelog entry below.

Also, if you are upgrading from a version earlier than 12.16, see Version 12.16.

 Changes

Postgres version 12.16 (end of life as of November 14, 2024)

Release date: 2023-08-10

This release contains a variety of fixes from 12.15. For information about new features in major release 12, see Version 12.0.

 Migration to Version 12.16

A dump/restore is not required for those running 12.X.

However, if you use BRIN indexes, it may be advisable to reindex them; see the second changelog entry below.

Also, if you are upgrading from a version earlier than 12.10, see Version 12.10.

 Changes

Postgres version 12.15 (end of life as of November 14, 2024)

Release date: 2023-05-11

This release contains a variety of fixes from 12.14. For information about new features in major release 12, see Version 12.0.

 Migration to Version 12.15

A dump/restore is not required for those running 12.X.

However, if you are upgrading from a version earlier than 12.10, see Version 12.10.

 Changes

Postgres version 12.14 (end of life as of November 14, 2024)

Release date: 2023-02-09

This release contains a variety of fixes from 12.13. For information about new features in major release 12, see Version 12.0.

 Migration to Version 12.14

A dump/restore is not required for those running 12.X.

However, if you are upgrading from a version earlier than 12.10, see Version 12.10.

 Changes

Postgres version 12.13 (end of life as of November 14, 2024)

Release date: 2022-11-10

This release contains a variety of fixes from 12.12. For information about new features in major release 12, see Version 12.0.

 Migration to Version 12.13

A dump/restore is not required for those running 12.X.

However, if you are upgrading from a version earlier than 12.10, see Version 12.10.

 Changes

Postgres version 12.12 (end of life as of November 14, 2024)

Release date: 2022-08-11

This release contains a variety of fixes from 12.11. For information about new features in major release 12, see Version 12.0.

 Migration to Version 12.12

A dump/restore is not required for those running 12.X.

However, if you are upgrading from a version earlier than 12.10, see Version 12.10.

 Changes

Postgres version 12.11 (end of life as of November 14, 2024)

Release date: 2022-05-12

This release contains a variety of fixes from 12.10. For information about new features in major release 12, see Version 12.0.

 Migration to Version 12.11

A dump/restore is not required for those running 12.X.

However, if you are upgrading from a version earlier than 12.10, see Version 12.10.

 Changes

Postgres version 12.10 (end of life as of November 14, 2024)

Release date: 2022-02-10

This release contains a variety of fixes from 12.9. For information about new features in major release 12, see Version 12.0.

 Migration to Version 12.10

A dump/restore is not required for those running 12.X.

However, if you have applied REINDEX CONCURRENTLY to a TOAST table's index, or observe failures to access TOAST datums, see the first changelog entry below.

Also, if you are upgrading from a version earlier than 12.9, see Version 12.9.

 Changes

Postgres version 12.9 (end of life as of November 14, 2024)

Release date: 2021-11-11

This release contains a variety of fixes from 12.8. For information about new features in major release 12, see Version 12.0.

 Migration to Version 12.9

A dump/restore is not required for those running 12.X.

However, note that installations using physical replication should update standby servers before the primary server, as explained in the third changelog entry below.

Also, several bugs have been found that may have resulted in corrupted indexes, as explained in the next several changelog entries. If any of those cases apply to you, it's recommended to reindex possibly-affected indexes after updating.

Also, if you are upgrading from a version earlier than 12.6, see Version 12.6.

 Changes

Postgres version 12.8 (end of life as of November 14, 2024)

Release date: 2021-08-12

This release contains a variety of fixes from 12.7. For information about new features in major release 12, see Version 12.0.

 Migration to Version 12.8

A dump/restore is not required for those running 12.X.

However, if you are upgrading from a version earlier than 12.6, see Version 12.6.

 Changes

Postgres version 12.7 (end of life as of November 14, 2024)

Release date: 2021-05-13

This release contains a variety of fixes from 12.6. For information about new features in major release 12, see Version 12.0.

 Migration to Version 12.7

A dump/restore is not required for those running 12.X.

However, if you are upgrading from a version earlier than 12.6, see Version 12.6.

 Changes

Postgres version 12.6 (end of life as of November 14, 2024)

Release date: 2021-02-11

This release contains a variety of fixes from 12.5. For information about new features in major release 12, see Version 12.0.

 Migration to Version 12.6

A dump/restore is not required for those running 12.X.

However, see the second and third changelog items below, which describe cases in which reindexing indexes after the upgrade may be advisable.

Also, if you are upgrading from a version earlier than 12.2, see Version 12.2.

 Changes

Postgres version 12.5 (end of life as of November 14, 2024)

Release date: 2020-11-12

This release contains a variety of fixes from 12.4. For information about new features in major release 12, see Version 12.0.

 Migration to Version 12.5

A dump/restore is not required for those running 12.X.

However, if you are upgrading from a version earlier than 12.2, see Version 12.2.

 Changes

Postgres version 12.4 (end of life as of November 14, 2024)

Release date: 2020-08-13

This release contains a variety of fixes from 12.3. For information about new features in major release 12, see Version 12.0.

 Migration to Version 12.4

A dump/restore is not required for those running 12.X.

However, if you are upgrading from a version earlier than 12.2, see Version 12.2.

 Changes

Postgres version 12.3 (end of life as of November 14, 2024)

Release date: 2020-05-14

This release contains a variety of fixes from 12.2. For information about new features in major release 12, see Version 12.0.

 Migration to Version 12.3

A dump/restore is not required for those running 12.X.

However, if you are upgrading from a version earlier than 12.2, see Version 12.2.

 Changes

Postgres version 12.2 (end of life as of November 14, 2024)

Release date: 2020-02-13

This release contains a variety of fixes from 12.1. For information about new features in major release 12, see Version 12.0.

 Migration to Version 12.2

A dump/restore is not required for those running 12.X.

However, if you have any foreign key constraints referencing partitioned tables, see the two entries below about bugs in that feature.

 Changes

Postgres version 12.1 (end of life as of November 14, 2024)

Release date: 2019-11-14

This release contains a variety of fixes from 12.0. For information about new features in major release 12, see Version 12.0.

 Migration to Version 12.1

A dump/restore is not required for those running 12.X.

 Changes

Postgres version 12.0 (end of life as of November 14, 2024)

Release date: 2019-10-03

 Overview

Major enhancements in PostgreSQL 12 include:

The above items are explained in more detail in the sections below.

 Migration to Version 12

A dump/restore using pg_dumpall or use of pg_upgrade or logical replication is required for those wishing to migrate data from any previous release. See Section 18.6 for general information on migrating to new major releases.

Version 12 contains a number of changes that may affect compatibility with previous releases. Observe the following incompatibilities:

 Changes

Below you will find a detailed account of the changes between PostgreSQL 12 and the previous major release.

 Server (PG 12.0)

 Partitioning (PG 12.0)

 Indexes (PG 12.0)

 Optimizer (PG 12.0)

 General Performance (PG 12.0)

 Monitoring (PG 12.0)

 Authentication (PG 12.0)

 Server Configuration (PG 12.0)

 Streaming Replication and Recovery (PG 12.0)

 Utility Commands (PG 12.0)

 Data Types (PG 12.0)

 Functions (PG 12.0)

 PL/pgSQL (PG 12.0)

 Client Interfaces (PG 12.0)

 Client Applications (PG 12.0)

 psql (PG 12.0)

 pgbench (PG 12.0)

 Server Applications (PG 12.0)

 pg_dump, pg_dumpall, pg_restore (PG 12.0)

 Source Code (PG 12.0)

 Additional Modules (PG 12.0)

 Acknowledgments

The following individuals (in alphabetical order) have contributed to this release as patch authors, committers, reviewers, testers, or reporters of issues.

Postgres version 11.22 (end of life as of November 9, 2023)

Release date: 2023-11-09

This release contains a variety of fixes from 11.21. For information about new features in major release 11, see Version 11.0.

This is expected to be the last PostgreSQL release in the 11.X series. Users are encouraged to update to a newer release branch soon.

 Migration to Version 11.22

A dump/restore is not required for those running 11.X.

However, if you are upgrading from a version earlier than 11.21, see Version 11.21.

 Changes

Postgres version 11.21 (end of life as of November 9, 2023)

Release date: 2023-08-10

This release contains a variety of fixes from 11.20. For information about new features in major release 11, see Version 11.0.

The PostgreSQL community will stop releasing updates for the 11.X release series in November 2023. Users are encouraged to update to a newer release branch soon.

 Migration to Version 11.21

A dump/restore is not required for those running 11.X.

However, if you use BRIN indexes, it may be advisable to reindex them; see the second changelog entry below.

Also, if you are upgrading from a version earlier than 11.14, see Version 11.14.

 Changes

Postgres version 11.20 (end of life as of November 9, 2023)

Release date: 2023-05-11

This release contains a variety of fixes from 11.19. For information about new features in major release 11, see Version 11.0.

The PostgreSQL community will stop releasing updates for the 11.X release series in November 2023. Users are encouraged to update to a newer release branch soon.

 Migration to Version 11.20

A dump/restore is not required for those running 11.X.

However, if you are upgrading from a version earlier than 11.14, see Version 11.14.

 Changes

Postgres version 11.19 (end of life as of November 9, 2023)

Release date: 2023-02-09

This release contains a variety of fixes from 11.18. For information about new features in major release 11, see Version 11.0.

The PostgreSQL community will stop releasing updates for the 11.X release series in November 2023. Users are encouraged to update to a newer release branch soon.

 Migration to Version 11.19

A dump/restore is not required for those running 11.X.

However, if you are upgrading from a version earlier than 11.14, see Version 11.14.

 Changes

Postgres version 11.18 (end of life as of November 9, 2023)

Release date: 2022-11-10

This release contains a variety of fixes from 11.17. For information about new features in major release 11, see Version 11.0.

 Migration to Version 11.18

A dump/restore is not required for those running 11.X.

However, if you are upgrading from a version earlier than 11.14, see Version 11.14.

 Changes

Postgres version 11.17 (end of life as of November 9, 2023)

Release date: 2022-08-11

This release contains a variety of fixes from 11.16. For information about new features in major release 11, see Version 11.0.

 Migration to Version 11.17

A dump/restore is not required for those running 11.X.

However, if you are upgrading from a version earlier than 11.14, see Version 11.14.

 Changes

Postgres version 11.16 (end of life as of November 9, 2023)

Release date: 2022-05-12

This release contains a variety of fixes from 11.15. For information about new features in major release 11, see Version 11.0.

 Migration to Version 11.16

A dump/restore is not required for those running 11.X.

However, if you are upgrading from a version earlier than 11.14, see Version 11.14.

 Changes

Postgres version 11.15 (end of life as of November 9, 2023)

Release date: 2022-02-10

This release contains a variety of fixes from 11.14. For information about new features in major release 11, see Version 11.0.

 Migration to Version 11.15

A dump/restore is not required for those running 11.X.

However, if you are upgrading from a version earlier than 11.14, see Version 11.14.

 Changes

Postgres version 11.14 (end of life as of November 9, 2023)

Release date: 2021-11-11

This release contains a variety of fixes from 11.13. For information about new features in major release 11, see Version 11.0.

 Migration to Version 11.14

A dump/restore is not required for those running 11.X.

However, note that installations using physical replication should update standby servers before the primary server, as explained in the third changelog entry below.

Also, several bugs have been found that may have resulted in corrupted indexes, as explained in the next several changelog entries. If any of those cases apply to you, it's recommended to reindex possibly-affected indexes after updating.

Also, if you are upgrading from a version earlier than 11.11, see Version 11.11.

 Changes

Postgres version 11.13 (end of life as of November 9, 2023)

Release date: 2021-08-12

This release contains a variety of fixes from 11.12. For information about new features in major release 11, see Version 11.0.

 Migration to Version 11.13

A dump/restore is not required for those running 11.X.

However, if you are upgrading from a version earlier than 11.11, see Version 11.11.

 Changes

Postgres version 11.12 (end of life as of November 9, 2023)

Release date: 2021-05-13

This release contains a variety of fixes from 11.11. For information about new features in major release 11, see Version 11.0.

 Migration to Version 11.12

A dump/restore is not required for those running 11.X.

However, if you are upgrading from a version earlier than 11.11, see Version 11.11.

 Changes

Postgres version 11.11 (end of life as of November 9, 2023)

Release date: 2021-02-11

This release contains a variety of fixes from 11.10. For information about new features in major release 11, see Version 11.0.

 Migration to Version 11.11

A dump/restore is not required for those running 11.X.

However, see the second changelog item below, which describes cases in which reindexing indexes after the upgrade may be advisable.

Also, if you are upgrading from a version earlier than 11.6, see Version 11.6.

 Changes

Postgres version 11.10 (end of life as of November 9, 2023)

Release date: 2020-11-12

This release contains a variety of fixes from 11.9. For information about new features in major release 11, see Version 11.0.

 Migration to Version 11.10

A dump/restore is not required for those running 11.X.

However, if you are upgrading from a version earlier than 11.6, see Version 11.6.

 Changes

Postgres version 11.9 (end of life as of November 9, 2023)

Release date: 2020-08-13

This release contains a variety of fixes from 11.8. For information about new features in major release 11, see Version 11.0.

 Migration to Version 11.9

A dump/restore is not required for those running 11.X.

However, if you are upgrading from a version earlier than 11.6, see Version 11.6.

 Changes

Postgres version 11.8 (end of life as of November 9, 2023)

Release date: 2020-05-14

This release contains a variety of fixes from 11.7. For information about new features in major release 11, see Version 11.0.

 Migration to Version 11.8

A dump/restore is not required for those running 11.X.

However, if you are upgrading from a version earlier than 11.6, see Version 11.6.

 Changes

Postgres version 11.7 (end of life as of November 9, 2023)

Release date: 2020-02-13

This release contains a variety of fixes from 11.6. For information about new features in major release 11, see Version 11.0.

 Migration to Version 11.7

A dump/restore is not required for those running 11.X.

However, if you are upgrading from a version earlier than 11.6, see Version 11.6.

 Changes

Postgres version 11.6 (end of life as of November 9, 2023)

Release date: 2019-11-14

This release contains a variety of fixes from 11.5. For information about new features in major release 11, see Version 11.0.

 Migration to Version 11.6

A dump/restore is not required for those running 11.X.

However, if you use the contrib/intarray extension with a GiST index, and you rely on indexed searches for the <@ operator, see the entry below about that.

Also, if you are upgrading from a version earlier than 11.1, see Version 11.1.

 Changes

Postgres version 11.5 (end of life as of November 9, 2023)

Release date: 2019-08-08

This release contains a variety of fixes from 11.4. For information about new features in major release 11, see Version 11.0.

 Migration to Version 11.5

A dump/restore is not required for those running 11.X.

However, if you are upgrading from a version earlier than 11.1, see Version 11.1.

 Changes

Postgres version 11.4 (end of life as of November 9, 2023)

Release date: 2019-06-20

This release contains a variety of fixes from 11.3. For information about new features in major release 11, see Version 11.0.

 Migration to Version 11.4

A dump/restore is not required for those running 11.X.

However, if you are upgrading from a version earlier than 11.1, see Version 11.1.

 Changes

Postgres version 11.3 (end of life as of November 9, 2023)

Release date: 2019-05-09

This release contains a variety of fixes from 11.2. For information about new features in major release 11, see Version 11.0.

 Migration to Version 11.3

A dump/restore is not required for those running 11.X.

However, if you are upgrading from a version earlier than 11.1, see Version 11.1.

 Changes

Postgres version 11.2 (end of life as of November 9, 2023)

Release date: 2019-02-14

This release contains a variety of fixes from 11.1. For information about new features in major release 11, see Version 11.0.

 Migration to Version 11.2

A dump/restore is not required for those running 11.X.

However, if you are upgrading from a version earlier than 11.1, see Version 11.1.

 Changes

Postgres version 11.1 (end of life as of November 9, 2023)

Release date: 2018-11-08

This release contains a variety of fixes from 11.0. For information about new features in major release 11, see Version 11.0.

 Migration to Version 11.1

A dump/restore is not required for those running 11.X.

However, if you use the pg_stat_statements extension, see the changelog entry below about that.

 Changes

Postgres version 11.0 (end of life as of November 9, 2023)

Release date: 2018-10-18

 Overview

Major enhancements in PostgreSQL 11 include:

The above items are explained in more detail in the sections below.

 Migration to Version 11

A dump/restore using pg_dumpall or use of pg_upgrade or logical replication is required for those wishing to migrate data from any previous release. See Section 18.6 for general information on migrating to new major releases.

Version 11 contains a number of changes that may affect compatibility with previous releases. Observe the following incompatibilities:

 Changes

Below you will find a detailed account of the changes between PostgreSQL 11 and the previous major release.

 Server (PG 11.0)

 Partitioning (PG 11.0)

 Parallel Queries (PG 11.0)

 Indexes (PG 11.0)

 SP-Gist (PG 11.0)

 Optimizer (PG 11.0)

 General Performance (PG 11.0)

 Monitoring (PG 11.0)

 Information Schema (PG 11.0)

 Authentication (PG 11.0)

 Permissions (PG 11.0)

 Server Configuration (PG 11.0)

 Write-Ahead Log (WAL) (PG 11.0)

 Base Backup and Streaming Replication (PG 11.0)

 Utility Commands (PG 11.0)

 Data Types (PG 11.0)

 Functions (PG 11.0)

 Server-Side Languages (PG 11.0)

 Client Interfaces (PG 11.0)

 Client Applications (PG 11.0)

 psql (PG 11.0)

 pgbench (PG 11.0)

 Server Applications (PG 11.0)

 pg_dump, pg_dumpall, pg_restore (PG 11.0)

 Source Code (PG 11.0)

 Additional Modules (PG 11.0)

 Acknowledgments

The following individuals (in alphabetical order) have contributed to this release as patch authors, committers, reviewers, testers, or reporters of issues.

Postgres version 10.23 (end of life as of November 10, 2022)

Release date: 2022-11-10

This release contains a variety of fixes from 10.22. For information about new features in major release 10, see Version 10.0.

This is expected to be the last PostgreSQL release in the 10.X series. Users are encouraged to update to a newer release branch soon.

 Migration to Version 10.23

A dump/restore is not required for those running 10.X.

However, if you are upgrading from a version earlier than 10.19, see Version 10.19.

 Changes

Postgres version 10.22 (end of life as of November 10, 2022)

Release date: 2022-08-11

This release contains a variety of fixes from 10.21. For information about new features in major release 10, see Version 10.0.

The PostgreSQL community will stop releasing updates for the 10.X release series in November 2022. Users are encouraged to update to a newer release branch soon.

 Migration to Version 10.22

A dump/restore is not required for those running 10.X.

However, if you are upgrading from a version earlier than 10.19, see Version 10.19.

 Changes

Postgres version 10.21 (end of life as of November 10, 2022)

Release date: 2022-05-12

This release contains a variety of fixes from 10.20. For information about new features in major release 10, see Version 10.0.

The PostgreSQL community will stop releasing updates for the 10.X release series in November 2022. Users are encouraged to update to a newer release branch soon.

 Migration to Version 10.21

A dump/restore is not required for those running 10.X.

However, if you are upgrading from a version earlier than 10.19, see Version 10.19.

 Changes

Postgres version 10.20 (end of life as of November 10, 2022)

Release date: 2022-02-10

This release contains a variety of fixes from 10.19. For information about new features in major release 10, see Version 10.0.

The PostgreSQL community will stop releasing updates for the 10.X release series in November 2022. Users are encouraged to update to a newer release branch soon.

 Migration to Version 10.20

A dump/restore is not required for those running 10.X.

However, if you are upgrading from a version earlier than 10.19, see Version 10.19.

 Changes

Postgres version 10.19 (end of life as of November 10, 2022)

Release date: 2021-11-11

This release contains a variety of fixes from 10.18. For information about new features in major release 10, see Version 10.0.

 Migration to Version 10.19

A dump/restore is not required for those running 10.X.

However, note that installations using physical replication should update standby servers before the primary server, as explained in the third changelog entry below.

Also, several bugs have been found that may have resulted in corrupted indexes, as explained in the next several changelog entries. If any of those cases apply to you, it's recommended to reindex possibly-affected indexes after updating.

Also, if you are upgrading from a version earlier than 10.16, see Version 10.16.

 Changes

Postgres version 10.18 (end of life as of November 10, 2022)

Release date: 2021-08-12

This release contains a variety of fixes from 10.17. For information about new features in major release 10, see Version 10.0.

 Migration to Version 10.18

A dump/restore is not required for those running 10.X.

However, if you are upgrading from a version earlier than 10.16, see Version 10.16.

 Changes

Postgres version 10.17 (end of life as of November 10, 2022)

Release date: 2021-05-13

This release contains a variety of fixes from 10.16. For information about new features in major release 10, see Version 10.0.

 Migration to Version 10.17

A dump/restore is not required for those running 10.X.

However, if you are upgrading from a version earlier than 10.16, see Version 10.16.

 Changes

Postgres version 10.16 (end of life as of November 10, 2022)

Release date: 2021-02-11

This release contains a variety of fixes from 10.15. For information about new features in major release 10, see Version 10.0.

 Migration to Version 10.16

A dump/restore is not required for those running 10.X.

However, see the first changelog item below, which describes cases in which reindexing indexes after the upgrade may be advisable.

Also, if you are upgrading from a version earlier than 10.11, see Version 10.11.

 Changes

Postgres version 10.15 (end of life as of November 10, 2022)

Release date: 2020-11-12

This release contains a variety of fixes from 10.14. For information about new features in major release 10, see Version 10.0.

 Migration to Version 10.15

A dump/restore is not required for those running 10.X.

However, if you are upgrading from a version earlier than 10.11, see Version 10.11.

 Changes

Postgres version 10.14 (end of life as of November 10, 2022)

Release date: 2020-08-13

This release contains a variety of fixes from 10.13. For information about new features in major release 10, see Version 10.0.

 Migration to Version 10.14

A dump/restore is not required for those running 10.X.

However, if you are upgrading from a version earlier than 10.11, see Version 10.11.

 Changes

Postgres version 10.13 (end of life as of November 10, 2022)

Release date: 2020-05-14

This release contains a variety of fixes from 10.12. For information about new features in major release 10, see Version 10.0.

 Migration to Version 10.13

A dump/restore is not required for those running 10.X.

However, if you are upgrading from a version earlier than 10.11, see Version 10.11.

 Changes

Postgres version 10.12 (end of life as of November 10, 2022)

Release date: 2020-02-13

This release contains a variety of fixes from 10.11. For information about new features in major release 10, see Version 10.0.

 Migration to Version 10.12

A dump/restore is not required for those running 10.X.

However, if you are upgrading from a version earlier than 10.11, see Version 10.11.

 Changes

Postgres version 10.11 (end of life as of November 10, 2022)

Release date: 2019-11-14

This release contains a variety of fixes from 10.10. For information about new features in major release 10, see Version 10.0.

 Migration to Version 10.11

A dump/restore is not required for those running 10.X.

However, if you use the contrib/intarray extension with a GiST index, and you rely on indexed searches for the <@ operator, see the entry below about that.

Also, if you are upgrading from a version earlier than 10.6, see Version 10.6.

 Changes

Postgres version 10.10 (end of life as of November 10, 2022)

Release date: 2019-08-08

This release contains a variety of fixes from 10.9. For information about new features in major release 10, see Version 10.0.

 Migration to Version 10.10

A dump/restore is not required for those running 10.X.

However, if you are upgrading from a version earlier than 10.6, see Version 10.6.

 Changes

Postgres version 10.9 (end of life as of November 10, 2022)

Release date: 2019-06-20

This release contains a variety of fixes from 10.8. For information about new features in major release 10, see Version 10.0.

 Migration to Version 10.9

A dump/restore is not required for those running 10.X.

However, if you are upgrading from a version earlier than 10.6, see Version 10.6.

 Changes

Postgres version 10.8 (end of life as of November 10, 2022)

Release date: 2019-05-09

This release contains a variety of fixes from 10.7. For information about new features in major release 10, see Version 10.0.

 Migration to Version 10.8

A dump/restore is not required for those running 10.X.

However, if you are upgrading from a version earlier than 10.6, see Version 10.6.

 Changes

Postgres version 10.7 (end of life as of November 10, 2022)

Release date: 2019-02-14

This release contains a variety of fixes from 10.6. For information about new features in major release 10, see Version 10.0.

 Migration to Version 10.7

A dump/restore is not required for those running 10.X.

However, if you are upgrading from a version earlier than 10.6, see Version 10.6.

 Changes

Postgres version 10.6 (end of life as of November 10, 2022)

Release date: 2018-11-08

This release contains a variety of fixes from 10.5. For information about new features in major release 10, see Version 10.0.

 Migration to Version 10.6

A dump/restore is not required for those running 10.X.

However, if you use the pg_stat_statements extension, see the changelog entry below about that.

Also, if you are upgrading from a version earlier than 10.4, see Version 10.4.

 Changes

Postgres version 10.5 (end of life as of November 10, 2022)

Release date: 2018-08-09

This release contains a variety of fixes from 10.4. For information about new features in major release 10, see Version 10.0.

 Migration to Version 10.5

A dump/restore is not required for those running 10.X.

However, if you are upgrading from a version earlier than 10.4, see Version 10.4.

 Changes

Postgres version 10.4 (end of life as of November 10, 2022)

Release date: 2018-05-10

This release contains a variety of fixes from 10.3. For information about new features in major release 10, see Version 10.0.

 Migration to Version 10.4

A dump/restore is not required for those running 10.X.

However, if you use the adminpack extension, you should update it as per the first changelog entry below.

Also, if the function marking mistakes mentioned in the second and third changelog entries below affect you, you will want to take steps to correct your database catalogs.

Also, if you are upgrading from a version earlier than 10.3, see Version 10.3.

 Changes

Postgres version 10.3 (end of life as of November 10, 2022)

Release date: 2018-03-01

This release contains a variety of fixes from 10.2. For information about new features in major release 10, see Version 10.0.

 Migration to Version 10.3

A dump/restore is not required for those running 10.X.

However, if you run an installation in which not all users are mutually trusting, or if you maintain an application or extension that is intended for use in arbitrary situations, it is strongly recommended that you read the documentation changes described in the first changelog entry below, and take suitable steps to ensure that your installation or code is secure.

Also, the changes described in the second changelog entry below may cause functions used in index expressions or materialized views to fail during auto-analyze, or when reloading from a dump. After upgrading, monitor the server logs for such problems, and fix affected functions.

Also, if you are upgrading from a version earlier than 10.2, see Version 10.2.

 Changes

Postgres version 10.2 (end of life as of November 10, 2022)

Release date: 2018-02-08

This release contains a variety of fixes from 10.1. For information about new features in major release 10, see Version 10.0.

 Migration to Version 10.2

A dump/restore is not required for those running 10.X.

However, if you use contrib/cube's ~> operator, see the entry below about that.

Also, if you are upgrading from a version earlier than 10.1, see Version 10.1.

 Changes

Postgres version 10.1 (end of life as of November 10, 2022)

Release date: 2017-11-09

This release contains a variety of fixes from 10.0. For information about new features in major release 10, see Version 10.0.

 Migration to Version 10.1

A dump/restore is not required for those running 10.X.

However, if you use BRIN indexes, see the fourth changelog entry below.

 Changes

Postgres version 10.0 (end of life as of November 10, 2022)

Release date: 2017-10-05

 Overview

Major enhancements in PostgreSQL 10 include:

The above items are explained in more detail in the sections below.

 Migration to Version 10

A dump/restore using pg_dumpall or use of pg_upgrade or logical replication is required for those wishing to migrate data from any previous release. See Section 18.6 for general information on migrating to new major releases.

Version 10 contains a number of changes that may affect compatibility with previous releases. Observe the following incompatibilities:

 Changes

Below you will find a detailed account of the changes between PostgreSQL 10 and the previous major release.

 Server (PG 10.0)

 Parallel Queries (PG 10.0)

 Indexes (PG 10.0)

 Locking (PG 10.0)

 Optimizer (PG 10.0)

 General Performance (PG 10.0)

 Monitoring (PG 10.0)

 Logging (PG 10.0)

 pg_stat_activity (PG 10.0)

 Authentication (PG 10.0)

 Server Configuration (PG 10.0)

 Reliability (PG 10.0)

 Write-Ahead Log (WAL) (PG 10.0)

 Replication and Recovery (PG 10.0)

 Queries (PG 10.0)

 Utility Commands (PG 10.0)

 Data Types (PG 10.0)

 Functions (PG 10.0)

 Server-Side Languages (PG 10.0)

 PL/Tcl (PG 10.0)

 Client Interfaces (PG 10.0)

 Client Applications (PG 10.0)

 psql (PG 10.0)

 pgbench (PG 10.0)

 Server Applications (PG 10.0)

 pg_dump, pg_dumpall, pg_restore (PG 10.0)

 pg_basebackup (PG 10.0)

 pg_ctl (PG 10.0)

 Source Code (PG 10.0)

 Additional Modules (PG 10.0)

 Acknowledgments

The following individuals (in alphabetical order) have contributed to this release as patch authors, committers, reviewers, testers, or reporters of issues.

Postgres version 9.6.24 (end of life as of November 11, 2021)

Release date: 2021-11-11

This release contains a variety of fixes from 9.6.23. For information about new features in the 9.6 major release, see Version 9.6.0.

This is expected to be the last PostgreSQL release in the 9.6.X series. Users are encouraged to update to a newer release branch soon.

Migration to Version 9.6.24

A dump/restore is not required for those running 9.6.X.

However, note that installations using physical replication should update standby servers before the primary server, as explained in the third changelog entry below.

Also, several bugs have been found that may have resulted in corrupted indexes, as explained in the next several changelog entries. If any of those cases apply to you, it's recommended to reindex possibly-affected indexes after updating.

Also, if you are upgrading from a version earlier than 9.6.21, see Version 9.6.21.

Changes

Postgres version 9.6.23 (end of life as of November 11, 2021)

Release date: 2021-08-12

This release contains a variety of fixes from 9.6.22. For information about new features in the 9.6 major release, see Version 9.6.0.

The PostgreSQL community will stop releasing updates for the 9.6.X release series in November 2021. Users are encouraged to update to a newer release branch soon.

Migration to Version 9.6.23

A dump/restore is not required for those running 9.6.X.

However, if you are upgrading from a version earlier than 9.6.21, see Version 9.6.21.

Changes

Postgres version 9.6.22 (end of life as of November 11, 2021)

Release date: 2021-05-13

This release contains a variety of fixes from 9.6.21. For information about new features in the 9.6 major release, see Version 9.6.0.

The PostgreSQL community will stop releasing updates for the 9.6.X release series in November 2021. Users are encouraged to update to a newer release branch soon.

Migration to Version 9.6.22

A dump/restore is not required for those running 9.6.X.

However, if you are upgrading from a version earlier than 9.6.21, see Version 9.6.21.

Changes

Postgres version 9.6.21 (end of life as of November 11, 2021)

Release date: 2021-02-11

This release contains a variety of fixes from 9.6.20. For information about new features in the 9.6 major release, see Version 9.6.0.

The PostgreSQL community will stop releasing updates for the 9.6.X release series in November 2021. Users are encouraged to update to a newer release branch soon.

Migration to Version 9.6.21

A dump/restore is not required for those running 9.6.X.

However, see the first changelog item below, which describes cases in which reindexing indexes after the upgrade may be advisable.

Also, if you are upgrading from a version earlier than 9.6.16, see Version 9.6.16.

Changes

Postgres version 9.6.20 (end of life as of November 11, 2021)

Release date: 2020-11-12

This release contains a variety of fixes from 9.6.19. For information about new features in the 9.6 major release, see Version 9.6.0.

Migration to Version 9.6.20

A dump/restore is not required for those running 9.6.X.

However, if you are upgrading from a version earlier than 9.6.16, see Version 9.6.16.

Changes

Postgres version 9.6.19 (end of life as of November 11, 2021)

Release date: 2020-08-13

This release contains a variety of fixes from 9.6.18. For information about new features in the 9.6 major release, see Version 9.6.0.

Migration to Version 9.6.19

A dump/restore is not required for those running 9.6.X.

However, if you are upgrading from a version earlier than 9.6.16, see Version 9.6.16.

Changes

Postgres version 9.6.18 (end of life as of November 11, 2021)

Release date: 2020-05-14

This release contains a variety of fixes from 9.6.17. For information about new features in the 9.6 major release, see Version 9.6.0.

Migration to Version 9.6.18

A dump/restore is not required for those running 9.6.X.

However, if you are upgrading from a version earlier than 9.6.16, see Version 9.6.16.

Changes

Postgres version 9.6.17 (end of life as of November 11, 2021)

Release date: 2020-02-13

This release contains a variety of fixes from 9.6.16. For information about new features in the 9.6 major release, see Version 9.6.0.

Migration to Version 9.6.17

A dump/restore is not required for those running 9.6.X.

However, if you are upgrading from a version earlier than 9.6.16, see Version 9.6.16.

Changes

Postgres version 9.6.16 (end of life as of November 11, 2021)

Release date: 2019-11-14

This release contains a variety of fixes from 9.6.15. For information about new features in the 9.6 major release, see Version 9.6.0.

Migration to Version 9.6.16

A dump/restore is not required for those running 9.6.X.

However, if you use the contrib/intarray extension with a GiST index, and you rely on indexed searches for the <@ operator, see the entry below about that.

Also, if you are upgrading from a version earlier than 9.6.9, see Version 9.6.9.

Changes

Postgres version 9.6.15 (end of life as of November 11, 2021)

Release date: 2019-08-08

This release contains a variety of fixes from 9.6.14. For information about new features in the 9.6 major release, see Version 9.6.0.

Migration to Version 9.6.15

A dump/restore is not required for those running 9.6.X.

However, if you are upgrading from a version earlier than 9.6.9, see Version 9.6.9.

Changes

Postgres version 9.6.14 (end of life as of November 11, 2021)

Release date: 2019-06-20

This release contains a variety of fixes from 9.6.13. For information about new features in the 9.6 major release, see Version 9.6.0.

Migration to Version 9.6.14

A dump/restore is not required for those running 9.6.X.

However, if you are upgrading from a version earlier than 9.6.9, see Version 9.6.9.

Changes

Postgres version 9.6.13 (end of life as of November 11, 2021)

Release date: 2019-05-09

This release contains a variety of fixes from 9.6.12. For information about new features in the 9.6 major release, see Version 9.6.0.

Migration to Version 9.6.13

A dump/restore is not required for those running 9.6.X.

However, if you are upgrading from a version earlier than 9.6.9, see Version 9.6.9.

Changes

Postgres version 9.6.12 (end of life as of November 11, 2021)

Release date: 2019-02-14

This release contains a variety of fixes from 9.6.11. For information about new features in the 9.6 major release, see Version 9.6.0.

Migration to Version 9.6.12

A dump/restore is not required for those running 9.6.X.

However, if you are upgrading from a version earlier than 9.6.9, see Version 9.6.9.

Changes

Postgres version 9.6.11 (end of life as of November 11, 2021)

Release date: 2018-11-08

This release contains a variety of fixes from 9.6.10. For information about new features in the 9.6 major release, see Version 9.6.0.

Migration to Version 9.6.11

A dump/restore is not required for those running 9.6.X.

However, if you are upgrading from a version earlier than 9.6.9, see Version 9.6.9.

Changes

Postgres version 9.6.10 (end of life as of November 11, 2021)

Release date: 2018-08-09

This release contains a variety of fixes from 9.6.9. For information about new features in the 9.6 major release, see Version 9.6.0.

Migration to Version 9.6.10

A dump/restore is not required for those running 9.6.X.

However, if you are upgrading from a version earlier than 9.6.9, see Version 9.6.9.

Changes

Postgres version 9.6.9 (end of life as of November 11, 2021)

Release date: 2018-05-10

This release contains a variety of fixes from 9.6.8. For information about new features in the 9.6 major release, see Version 9.6.0.

Migration to Version 9.6.9

A dump/restore is not required for those running 9.6.X.

However, if you use the adminpack extension, you should update it as per the first changelog entry below.

Also, if the function marking mistakes mentioned in the second and third changelog entries below affect you, you will want to take steps to correct your database catalogs.

Also, if you are upgrading from a version earlier than 9.6.8, see Version 9.6.8.

Changes

Postgres version 9.6.8 (end of life as of November 11, 2021)

Release date: 2018-03-01

This release contains a variety of fixes from 9.6.7. For information about new features in the 9.6 major release, see Version 9.6.0.

Migration to Version 9.6.8

A dump/restore is not required for those running 9.6.X.

However, if you run an installation in which not all users are mutually trusting, or if you maintain an application or extension that is intended for use in arbitrary situations, it is strongly recommended that you read the documentation changes described in the first changelog entry below, and take suitable steps to ensure that your installation or code is secure.

Also, the changes described in the second changelog entry below may cause functions used in index expressions or materialized views to fail during auto-analyze, or when reloading from a dump. After upgrading, monitor the server logs for such problems, and fix affected functions.

Also, if you are upgrading from a version earlier than 9.6.7, see Version 9.6.7.

Changes

Postgres version 9.6.7 (end of life as of November 11, 2021)

Release date: 2018-02-08

This release contains a variety of fixes from 9.6.6. For information about new features in the 9.6 major release, see Version 9.6.0.

Migration to Version 9.6.7

A dump/restore is not required for those running 9.6.X.

However, if you use contrib/cube's ~> operator, see the entry below about that.

Also, if you are upgrading from a version earlier than 9.6.6, see Version 9.6.6.

Changes

Postgres version 9.6.6 (end of life as of November 11, 2021)

Release date: 2017-11-09

This release contains a variety of fixes from 9.6.5. For information about new features in the 9.6 major release, see Version 9.6.0.

Migration to Version 9.6.6

A dump/restore is not required for those running 9.6.X.

However, if you use BRIN indexes, see the fourth changelog entry below.

Also, if you are upgrading from a version earlier than 9.6.4, see Version 9.6.4.

Changes

Postgres version 9.6.5 (end of life as of November 11, 2021)

Release date: 2017-08-31

This release contains a small number of fixes from 9.6.4. For information about new features in the 9.6 major release, see Version 9.6.0.

Migration to Version 9.6.5

A dump/restore is not required for those running 9.6.X.

However, if you are upgrading from a version earlier than 9.6.4, see Version 9.6.4.

Changes

Postgres version 9.6.4 (end of life as of November 11, 2021)

Release date: 2017-08-10

This release contains a variety of fixes from 9.6.3. For information about new features in the 9.6 major release, see Version 9.6.0.

Migration to Version 9.6.4

A dump/restore is not required for those running 9.6.X.

However, if you use foreign data servers that make use of user passwords for authentication, see the first changelog entry below.

Also, if you are upgrading from a version earlier than 9.6.3, see Version 9.6.3.

Changes

Postgres version 9.6.3 (end of life as of November 11, 2021)

Release date: 2017-05-11

This release contains a variety of fixes from 9.6.2. For information about new features in the 9.6 major release, see Version 9.6.0.

Migration to Version 9.6.3

A dump/restore is not required for those running 9.6.X.

However, if you use foreign data servers that make use of user passwords for authentication, see the first changelog entry below.

Also, if you are using third-party replication tools that depend on "logical decoding", see the fourth changelog entry below.

Also, if you are upgrading from a version earlier than 9.6.2, see Version 9.6.2.

Changes

Postgres version 9.6.2 (end of life as of November 11, 2021)

Release date: 2017-02-09

This release contains a variety of fixes from 9.6.1. For information about new features in the 9.6 major release, see Version 9.6.0.

Migration to Version 9.6.2

A dump/restore is not required for those running 9.6.X.

However, if your installation has been affected by the bug described in the first changelog entry below, then after updating you may need to take action to repair corrupted indexes.

Also, if you are upgrading from a version earlier than 9.6.1, see Version 9.6.1.

Changes

Postgres version 9.6.1 (end of life as of November 11, 2021)

Release date: 2016-10-27

This release contains a variety of fixes from 9.6.0. For information about new features in the 9.6 major release, see Version 9.6.0.

Migration to Version 9.6.1

A dump/restore is not required for those running 9.6.X.

However, if your installation has been affected by the bugs described in the first two changelog entries below, then after updating you may need to take action to repair corrupted free space maps and/or visibility maps.

Changes

Postgres version 9.6.0 (end of life as of November 11, 2021)

Release date: 2016-09-29

Overview

Major enhancements in PostgreSQL 9.6 include:

The above items are explained in more detail in the sections below.

Migration to Version 9.6

A dump/restore using pg_dumpall, or use of pg_upgrade, is required for those wishing to migrate data from any previous release.

Version 9.6 contains a number of changes that may affect compatibility with previous releases. Observe the following incompatibilities:

Changes

Below you will find a detailed account of the changes between PostgreSQL 9.6 and the previous major release.

Server

Parallel Queries (PG 9.6.0)

Indexes (PG 9.6.0)

Sorting (PG 9.6.0)

Locking (PG 9.6.0)

Optimizer Statistics (PG 9.6.0)

VACUUM (PG 9.6.0)

General Performance (PG 9.6.0)

Monitoring (PG 9.6.0)

Authentication (PG 9.6.0)

Server Configuration (PG 9.6.0)

Reliability (PG 9.6.0)

Replication and Recovery

Queries

Utility Commands

Permissions Management

Data Types

Functions

Server-Side Languages

Client Interfaces

Client Applications

psql (PG 9.6.0)

pgbench (PG 9.6.0)

Server Applications

Source Code

Additional Modules

postgres_fdw (PG 9.6.0)

Postgres version 9.5.25 (end of life as of February 11, 2021)

Release date: 2021-02-11

This release contains a variety of fixes from 9.5.24. For information about new features in the 9.5 major release, see Version 9.5.0.

This is expected to be the last PostgreSQL release in the 9.5.X series. Users are encouraged to update to a newer release branch soon.

Migration to Version 9.5.25

A dump/restore is not required for those running 9.5.X.

However, see the first changelog item below, which describes cases in which reindexing indexes after the upgrade may be advisable.

Also, if you are upgrading from a version earlier than 9.5.20, see Version 9.5.20.

Changes

Postgres version 9.5.24 (end of life as of February 11, 2021)

Release date: 2020-11-12

This release contains a variety of fixes from 9.5.23. For information about new features in the 9.5 major release, see Version 9.5.0.

The PostgreSQL community will stop releasing updates for the 9.5.X release series in February 2021. Users are encouraged to update to a newer release branch soon.

Migration to Version 9.5.24

A dump/restore is not required for those running 9.5.X.

However, if you are upgrading from a version earlier than 9.5.20, see Version 9.5.20.

Changes

Postgres version 9.5.23 (end of life as of February 11, 2021)

Release date: 2020-08-13

This release contains a variety of fixes from 9.5.22. For information about new features in the 9.5 major release, see Version 9.5.0.

The PostgreSQL community will stop releasing updates for the 9.5.X release series in February 2021. Users are encouraged to update to a newer release branch soon.

Migration to Version 9.5.23

A dump/restore is not required for those running 9.5.X.

However, if you are upgrading from a version earlier than 9.5.20, see Version 9.5.20.

Changes

Postgres version 9.5.22 (end of life as of February 11, 2021)

Release date: 2020-05-14

This release contains a variety of fixes from 9.5.21. For information about new features in the 9.5 major release, see Version 9.5.0.

The PostgreSQL community will stop releasing updates for the 9.5.X release series in February 2021. Users are encouraged to update to a newer release branch soon.

Migration to Version 9.5.22

A dump/restore is not required for those running 9.5.X.

However, if you are upgrading from a version earlier than 9.5.20, see Version 9.5.20.

Changes

Postgres version 9.5.21 (end of life as of February 11, 2021)

Release date: 2020-02-13

This release contains a variety of fixes from 9.5.20. For information about new features in the 9.5 major release, see Version 9.5.0.

Migration to Version 9.5.21

A dump/restore is not required for those running 9.5.X.

However, if you are upgrading from a version earlier than 9.5.20, see Version 9.5.20.

Changes

Postgres version 9.5.20 (end of life as of February 11, 2021)

Release date: 2019-11-14

This release contains a variety of fixes from 9.5.19. For information about new features in the 9.5 major release, see Version 9.5.0.

Migration to Version 9.5.20

A dump/restore is not required for those running 9.5.X.

However, if you use the contrib/intarray extension with a GiST index, and you rely on indexed searches for the <@ operator, see the entry below about that.

Also, if you are upgrading from a version earlier than 9.5.13, see Version 9.5.13.

Changes

Postgres version 9.5.19 (end of life as of February 11, 2021)

Release date: 2019-08-08

This release contains a variety of fixes from 9.5.18. For information about new features in the 9.5 major release, see Version 9.5.0.

Migration to Version 9.5.19

A dump/restore is not required for those running 9.5.X.

However, if you are upgrading from a version earlier than 9.5.13, see Version 9.5.13.

Changes

Postgres version 9.5.18 (end of life as of February 11, 2021)

Release date: 2019-06-20

This release contains a variety of fixes from 9.5.17. For information about new features in the 9.5 major release, see Version 9.5.0.

Migration to Version 9.5.18

A dump/restore is not required for those running 9.5.X.

However, if you are upgrading from a version earlier than 9.5.13, see Version 9.5.13.

Changes

Postgres version 9.5.17 (end of life as of February 11, 2021)

Release date: 2019-05-09

This release contains a variety of fixes from 9.5.16. For information about new features in the 9.5 major release, see Version 9.5.0.

Migration to Version 9.5.17

A dump/restore is not required for those running 9.5.X.

However, if you are upgrading from a version earlier than 9.5.13, see Version 9.5.13.

Changes

Postgres version 9.5.16 (end of life as of February 11, 2021)

Release date: 2019-02-14

This release contains a variety of fixes from 9.5.15. For information about new features in the 9.5 major release, see Version 9.5.0.

Migration to Version 9.5.16

A dump/restore is not required for those running 9.5.X.

However, if you are upgrading from a version earlier than 9.5.13, see Version 9.5.13.

Changes

Postgres version 9.5.15 (end of life as of February 11, 2021)

Release date: 2018-11-08

This release contains a variety of fixes from 9.5.14. For information about new features in the 9.5 major release, see Version 9.5.0.

Migration to Version 9.5.15

A dump/restore is not required for those running 9.5.X.

However, if you are upgrading from a version earlier than 9.5.13, see Version 9.5.13.

Changes

Postgres version 9.5.14 (end of life as of February 11, 2021)

Release date: 2018-08-09

This release contains a variety of fixes from 9.5.13. For information about new features in the 9.5 major release, see Version 9.5.0.

Migration to Version 9.5.14

A dump/restore is not required for those running 9.5.X.

However, if you are upgrading from a version earlier than 9.5.13, see Version 9.5.13.

Changes

Postgres version 9.5.13 (end of life as of February 11, 2021)

Release date: 2018-05-10

This release contains a variety of fixes from 9.5.12. For information about new features in the 9.5 major release, see Version 9.5.0.

Migration to Version 9.5.13

A dump/restore is not required for those running 9.5.X.

However, if the function marking mistakes mentioned in the first changelog entry below affect you, you will want to take steps to correct your database catalogs.

Also, if you are upgrading from a version earlier than 9.5.12, see Version 9.5.12.

Changes

Postgres version 9.5.12 (end of life as of February 11, 2021)

Release date: 2018-03-01

This release contains a variety of fixes from 9.5.11. For information about new features in the 9.5 major release, see Version 9.5.0.

Migration to Version 9.5.12

A dump/restore is not required for those running 9.5.X.

However, if you run an installation in which not all users are mutually trusting, or if you maintain an application or extension that is intended for use in arbitrary situations, it is strongly recommended that you read the documentation changes described in the first changelog entry below, and take suitable steps to ensure that your installation or code is secure.

Also, the changes described in the second changelog entry below may cause functions used in index expressions or materialized views to fail during auto-analyze, or when reloading from a dump. After upgrading, monitor the server logs for such problems, and fix affected functions.

Also, if you are upgrading from a version earlier than 9.5.10, see Version 9.5.10.

Changes

Postgres version 9.5.11 (end of life as of February 11, 2021)

Release date: 2018-02-08

This release contains a variety of fixes from 9.5.10. For information about new features in the 9.5 major release, see Version 9.5.0.

Migration to Version 9.5.11

A dump/restore is not required for those running 9.5.X.

However, if you are upgrading from a version earlier than 9.5.10, see Version 9.5.10.

Changes

Postgres version 9.5.10 (end of life as of February 11, 2021)

Release date: 2017-11-09

This release contains a variety of fixes from 9.5.9. For information about new features in the 9.5 major release, see Version 9.5.0.

Migration to Version 9.5.10

A dump/restore is not required for those running 9.5.X.

However, if you use BRIN indexes, see the fourth changelog entry below.

Also, if you are upgrading from a version earlier than 9.5.8, see Version 9.5.8.

Changes

Postgres version 9.5.9 (end of life as of February 11, 2021)

Release date: 2017-08-31

This release contains a small number of fixes from 9.5.8. For information about new features in the 9.5 major release, see Version 9.5.0.

Migration to Version 9.5.9

A dump/restore is not required for those running 9.5.X.

However, if you are upgrading from a version earlier than 9.5.8, see Version 9.5.8.

Changes

Postgres version 9.5.8 (end of life as of February 11, 2021)

Release date: 2017-08-10

This release contains a variety of fixes from 9.5.7. For information about new features in the 9.5 major release, see Version 9.5.0.

Migration to Version 9.5.8

A dump/restore is not required for those running 9.5.X.

However, if you use foreign data servers that make use of user passwords for authentication, see the first changelog entry below.

Also, if you are upgrading from a version earlier than 9.5.7, see Version 9.5.7.

Changes

Postgres version 9.5.7 (end of life as of February 11, 2021)

Release date: 2017-05-11

This release contains a variety of fixes from 9.5.6. For information about new features in the 9.5 major release, see Version 9.5.0.

Migration to Version 9.5.7

A dump/restore is not required for those running 9.5.X.

However, if you use foreign data servers that make use of user passwords for authentication, see the first changelog entry below.

Also, if you are using third-party replication tools that depend on "logical decoding", see the fourth changelog entry below.

Also, if you are upgrading from a version earlier than 9.5.6, see Version 9.5.6.

Changes

Postgres version 9.5.6 (end of life as of February 11, 2021)

Release date: 2017-02-09

This release contains a variety of fixes from 9.5.5. For information about new features in the 9.5 major release, see Version 9.5.0.

Migration to Version 9.5.6

A dump/restore is not required for those running 9.5.X.

However, if your installation has been affected by the bug described in the first changelog entry below, then after updating you may need to take action to repair corrupted indexes.

Also, if you are upgrading from a version earlier than 9.5.5, see Version 9.5.5.

Changes

Postgres version 9.5.5 (end of life as of February 11, 2021)

Release date: 2016-10-27

This release contains a variety of fixes from 9.5.4. For information about new features in the 9.5 major release, see Version 9.5.0.

Migration to Version 9.5.5

A dump/restore is not required for those running 9.5.X.

However, if your installation has been affected by the bug described in the first changelog entry below, then after updating you may need to take action to repair corrupted free space maps.

Also, if you are upgrading from a version earlier than 9.5.2, see Version 9.5.2.

Changes

Postgres version 9.5.4 (end of life as of February 11, 2021)

Release date: 2016-08-11

This release contains a variety of fixes from 9.5.3. For information about new features in the 9.5 major release, see Version 9.5.0.

Migration to Version 9.5.4

A dump/restore is not required for those running 9.5.X.

However, if you are upgrading from a version earlier than 9.5.2, see Version 9.5.2.

Changes

Postgres version 9.5.3 (end of life as of February 11, 2021)

Release date: 2016-05-12

This release contains a variety of fixes from 9.5.2. For information about new features in the 9.5 major release, see Version 9.5.0.

Migration to Version 9.5.3

A dump/restore is not required for those running 9.5.X.

However, if you are upgrading from a version earlier than 9.5.2, see Version 9.5.2.

Changes

Postgres version 9.5.2 (end of life as of February 11, 2021)

Release date: 2016-03-31

This release contains a variety of fixes from 9.5.1. For information about new features in the 9.5 major release, see Version 9.5.0.

Migration to Version 9.5.2

A dump/restore is not required for those running 9.5.X.

However, you may need to REINDEX some indexes after applying the update, as per the first changelog entry below.

Changes

Postgres version 9.5.1 (end of life as of February 11, 2021)

Release date: 2016-02-11

This release contains a variety of fixes from 9.5.0. For information about new features in the 9.5 major release, see Version 9.5.0.

Migration to Version 9.5.1

A dump/restore is not required for those running 9.5.X.

Changes

Postgres version 9.5.0 (end of life as of February 11, 2021)

Release date: 2016-01-07

Overview

Major enhancements in PostgreSQL 9.5 include:

The above items are explained in more detail in the sections below.

Migration to Version 9.5

A dump/restore using pg_dumpall, or use of pg_upgrade, is required for those wishing to migrate data from any previous release.

Version 9.5 contains a number of changes that may affect compatibility with previous releases. Observe the following incompatibilities:

Changes

Below you will find a detailed account of the changes between PostgreSQL 9.5 and the previous major release.

Server

Indexes (PG 9.5.0)

General Performance (PG 9.5.0)

Monitoring (PG 9.5.0)

SSL (PG 9.5.0)

Server Settings (PG 9.5.0)

Replication and Recovery

Queries

Utility Commands

REINDEX (PG 9.5.0)

Object Manipulation

Foreign Tables (PG 9.5.0)

Event Triggers (PG 9.5.0)

Data Types

JSON (PG 9.5.0)

Functions

System Information Functions and Views (PG 9.5.0)

Aggregates (PG 9.5.0)

Server-Side Languages

PL/pgSQL Server-Side Language (PG 9.5.0)

Client Applications

psql (PG 9.5.0)

Backslash Commands (PG 9.5.0)

pg_dump (PG 9.5.0)

pg_ctl (PG 9.5.0)

pg_upgrade (PG 9.5.0)

pgbench (PG 9.5.0)

Source Code

MS Windows (PG 9.5.0)

Additional Modules

Postgres version 9.4.26 (end of life as of February 13, 2020)

Release date: 2020-02-13

This release contains a variety of fixes from 9.4.25. For information about new features in the 9.4 major release, see Version 9.4.0.

This is expected to be the last PostgreSQL release in the 9.4.X series. Users are encouraged to update to a newer release branch soon.

Migration to Version 9.4.26

A dump/restore is not required for those running 9.4.X.

However, if you are upgrading from a version earlier than 9.4.25, see Version 9.4.25.

Changes

Postgres version 9.4.25 (end of life as of February 13, 2020)

Release date: 2019-11-14

This release contains a variety of fixes from 9.4.24. For information about new features in the 9.4 major release, see Version 9.4.0.

The PostgreSQL community will stop releasing updates for the 9.4.X release series in February 2020. Users are encouraged to update to a newer release branch soon.

Migration to Version 9.4.25

A dump/restore is not required for those running 9.4.X.

However, if you use the contrib/intarray extension with a GiST index, and you rely on indexed searches for the <@ operator, see the entry below about that.

Also, if you are upgrading from a version earlier than 9.4.18, see Version 9.4.18.

Changes

Postgres version 9.4.24 (end of life as of February 13, 2020)

Release date: 2019-08-08

This release contains a variety of fixes from 9.4.23. For information about new features in the 9.4 major release, see Version 9.4.0.

The PostgreSQL community will stop releasing updates for the 9.4.X release series in February 2020. Users are encouraged to update to a newer release branch soon.

Migration to Version 9.4.24

A dump/restore is not required for those running 9.4.X.

However, if you are upgrading from a version earlier than 9.4.18, see Version 9.4.18.

Changes

Postgres version 9.4.23 (end of life as of February 13, 2020)

Release date: 2019-06-20

This release contains a variety of fixes from 9.4.22. For information about new features in the 9.4 major release, see Version 9.4.0.

The PostgreSQL community will stop releasing updates for the 9.4.X release series in February 2020. Users are encouraged to update to a newer release branch soon.

Migration to Version 9.4.23

A dump/restore is not required for those running 9.4.X.

However, if you are upgrading from a version earlier than 9.4.18, see Version 9.4.18.

Changes

Postgres version 9.4.22 (end of life as of February 13, 2020)

Release date: 2019-05-09

This release contains a variety of fixes from 9.4.21. For information about new features in the 9.4 major release, see Version 9.4.0.

The PostgreSQL community will stop releasing updates for the 9.4.X release series in February 2020. Users are encouraged to update to a newer release branch soon.

Migration to Version 9.4.22

A dump/restore is not required for those running 9.4.X.

However, if you are upgrading from a version earlier than 9.4.18, see Version 9.4.18.

Changes

Postgres version 9.4.21 (end of life as of February 13, 2020)

Release date: 2019-02-14

This release contains a variety of fixes from 9.4.20. For information about new features in the 9.4 major release, see Version 9.4.0.

The PostgreSQL community will stop releasing updates for the 9.4.X release series in February 2020. Users are encouraged to update to a newer release branch soon.

Migration to Version 9.4.21

A dump/restore is not required for those running 9.4.X.

However, if you are upgrading from a version earlier than 9.4.18, see Version 9.4.18.

Changes

Postgres version 9.4.20 (end of life as of February 13, 2020)

Release date: 2018-11-08

This release contains a variety of fixes from 9.4.19. For information about new features in the 9.4 major release, see Version 9.4.0.

Migration to Version 9.4.20

A dump/restore is not required for those running 9.4.X.

However, if you are upgrading from a version earlier than 9.4.18, see Version 9.4.18.

Changes

Postgres version 9.4.19 (end of life as of February 13, 2020)

Release date: 2018-08-09

This release contains a variety of fixes from 9.4.18. For information about new features in the 9.4 major release, see Version 9.4.0.

Migration to Version 9.4.19

A dump/restore is not required for those running 9.4.X.

However, if you are upgrading from a version earlier than 9.4.18, see Version 9.4.18.

Changes

Postgres version 9.4.18 (end of life as of February 13, 2020)

Release date: 2018-05-10

This release contains a variety of fixes from 9.4.17. For information about new features in the 9.4 major release, see Version 9.4.0.

Migration to Version 9.4.18

A dump/restore is not required for those running 9.4.X.

However, if the function marking mistakes mentioned in the first changelog entry below affect you, you will want to take steps to correct your database catalogs.

Also, if you are upgrading from a version earlier than 9.4.17, see Version 9.4.17.

Changes

Postgres version 9.4.17 (end of life as of February 13, 2020)

Release date: 2018-03-01

This release contains a variety of fixes from 9.4.16. For information about new features in the 9.4 major release, see Version 9.4.0.

Migration to Version 9.4.17

A dump/restore is not required for those running 9.4.X.

However, if you run an installation in which not all users are mutually trusting, or if you maintain an application or extension that is intended for use in arbitrary situations, it is strongly recommended that you read the documentation changes described in the first changelog entry below, and take suitable steps to ensure that your installation or code is secure.

Also, the changes described in the second changelog entry below may cause functions used in index expressions or materialized views to fail during auto-analyze, or when reloading from a dump. After upgrading, monitor the server logs for such problems, and fix affected functions.

Also, if you are upgrading from a version earlier than 9.4.13, see Version 9.4.13.

Changes

Postgres version 9.4.16 (end of life as of February 13, 2020)

Release date: 2018-02-08

This release contains a variety of fixes from 9.4.15. For information about new features in the 9.4 major release, see Version 9.4.0.

Migration to Version 9.4.16

A dump/restore is not required for those running 9.4.X.

However, if you are upgrading from a version earlier than 9.4.13, see Version 9.4.13.

Changes

Postgres version 9.4.15 (end of life as of February 13, 2020)

Release date: 2017-11-09

This release contains a variety of fixes from 9.4.14. For information about new features in the 9.4 major release, see Version 9.4.0.

Migration to Version 9.4.15

A dump/restore is not required for those running 9.4.X.

However, if you are upgrading from a version earlier than 9.4.13, see Version 9.4.13.

Changes

Postgres version 9.4.14 (end of life as of February 13, 2020)

Release date: 2017-08-31

This release contains a small number of fixes from 9.4.13. For information about new features in the 9.4 major release, see Version 9.4.0.

Migration to Version 9.4.14

A dump/restore is not required for those running 9.4.X.

However, if you are upgrading from a version earlier than 9.4.13, see Version 9.4.13.

Changes

Postgres version 9.4.13 (end of life as of February 13, 2020)

Release date: 2017-08-10

This release contains a variety of fixes from 9.4.12. For information about new features in the 9.4 major release, see Version 9.4.0.

Migration to Version 9.4.13

A dump/restore is not required for those running 9.4.X.

However, if you use foreign data servers that make use of user passwords for authentication, see the first changelog entry below.

Also, if you are upgrading from a version earlier than 9.4.12, see Version 9.4.12.

Changes

Postgres version 9.4.12 (end of life as of February 13, 2020)

Release date: 2017-05-11

This release contains a variety of fixes from 9.4.11. For information about new features in the 9.4 major release, see Version 9.4.0.

Migration to Version 9.4.12

A dump/restore is not required for those running 9.4.X.

However, if you use foreign data servers that make use of user passwords for authentication, see the first changelog entry below.

Also, if you are using third-party replication tools that depend on "logical decoding", see the fourth changelog entry below.

Also, if you are upgrading from a version earlier than 9.4.11, see Version 9.4.11.

Changes

Postgres version 9.4.11 (end of life as of February 13, 2020)

Release date: 2017-02-09

This release contains a variety of fixes from 9.4.10. For information about new features in the 9.4 major release, see Version 9.4.0.

Migration to Version 9.4.11

A dump/restore is not required for those running 9.4.X.

However, if your installation has been affected by the bug described in the first changelog entry below, then after updating you may need to take action to repair corrupted indexes.

Also, if you are upgrading from a version earlier than 9.4.10, see Version 9.4.10.

Changes

Postgres version 9.4.10 (end of life as of February 13, 2020)

Release date: 2016-10-27

This release contains a variety of fixes from 9.4.9. For information about new features in the 9.4 major release, see Version 9.4.0.

Migration to Version 9.4.10

A dump/restore is not required for those running 9.4.X.

However, if your installation has been affected by the bug described in the first changelog entry below, then after updating you may need to take action to repair corrupted free space maps.

Also, if you are upgrading from a version earlier than 9.4.6, see Version 9.4.6.

Changes

Postgres version 9.4.9 (end of life as of February 13, 2020)

Release date: 2016-08-11

This release contains a variety of fixes from 9.4.8. For information about new features in the 9.4 major release, see Version 9.4.0.

Migration to Version 9.4.9

A dump/restore is not required for those running 9.4.X.

However, if you are upgrading from a version earlier than 9.4.6, see Version 9.4.6.

Changes

Postgres version 9.4.8 (end of life as of February 13, 2020)

Release date: 2016-05-12

This release contains a variety of fixes from 9.4.7. For information about new features in the 9.4 major release, see Version 9.4.0.

Migration to Version 9.4.8

A dump/restore is not required for those running 9.4.X.

However, if you are upgrading from a version earlier than 9.4.6, see Version 9.4.6.

Changes

Postgres version 9.4.7 (end of life as of February 13, 2020)

Release date: 2016-03-31

This release contains a variety of fixes from 9.4.6. For information about new features in the 9.4 major release, see Version 9.4.0.

Migration to Version 9.4.7

A dump/restore is not required for those running 9.4.X.

However, if you are upgrading from a version earlier than 9.4.6, see Version 9.4.6.

Changes

Postgres version 9.4.6 (end of life as of February 13, 2020)

Release date: 2016-02-11

This release contains a variety of fixes from 9.4.5. For information about new features in the 9.4 major release, see Version 9.4.0.

Migration to Version 9.4.6

A dump/restore is not required for those running 9.4.X.

However, if you are upgrading an installation that contains any GIN indexes that use the (non-default) jsonb_path_ops operator class, see the first changelog entry below.

Also, if you are upgrading from a version earlier than 9.4.4, see Version 9.4.4.

Changes

Postgres version 9.4.5 (end of life as of February 13, 2020)

Release date: 2015-10-08

This release contains a variety of fixes from 9.4.4. For information about new features in the 9.4 major release, see Version 9.4.0.

Migration to Version 9.4.5

A dump/restore is not required for those running 9.4.X.

However, if you are upgrading from a version earlier than 9.4.4, see Version 9.4.4.

Changes

Postgres version 9.4.4 (end of life as of February 13, 2020)

Release date: 2015-06-12

This release contains a small number of fixes from 9.4.3. For information about new features in the 9.4 major release, see Version 9.4.0.

Migration to Version 9.4.4

A dump/restore is not required for those running 9.4.X.

However, if you are upgrading an installation that was previously upgraded using a pg_upgrade version between 9.3.0 and 9.3.4 inclusive, see the first changelog entry below.

Also, if you are upgrading from a version earlier than 9.4.2, see Version 9.4.2.

Changes

Postgres version 9.4.3 (end of life as of February 13, 2020)

Release date: 2015-06-04

This release contains a small number of fixes from 9.4.2. For information about new features in the 9.4 major release, see Version 9.4.0.

Migration to Version 9.4.3

A dump/restore is not required for those running 9.4.X.

However, if you are upgrading from a version earlier than 9.4.2, see Version 9.4.2.

Changes

Postgres version 9.4.2 (end of life as of February 13, 2020)

Release date: 2015-05-22

This release contains a variety of fixes from 9.4.1. For information about new features in the 9.4 major release, see Version 9.4.0.

Migration to Version 9.4.2

A dump/restore is not required for those running 9.4.X.

However, if you use contrib/citext's regexp_matches() functions, see the changelog entry below about that.

Also, if you are upgrading from a version earlier than 9.4.1, see Version 9.4.1.

Changes

Postgres version 9.4.1 (end of life as of February 13, 2020)

Release date: 2015-02-05

This release contains a variety of fixes from 9.4.0. For information about new features in the 9.4 major release, see Version 9.4.0.

Migration to Version 9.4.1

A dump/restore is not required for those running 9.4.X.

However, if you are a Windows user and are using the "Norwegian (BokmĂĽl)" locale, manual action is needed after the upgrade to replace any "Norwegian (BokmĂĽl)_Norway" or "norwegian-bokmal" locale names stored in PostgreSQL system catalogs with the plain-ASCII alias "Norwegian_Norway". For details see http://wiki.postgresql.org/wiki/Changes_To_Norwegian_Locale

Changes

Postgres version 9.4.0 (end of life as of February 13, 2020)

Release date: 2014-12-18

Overview

Major enhancements in PostgreSQL 9.4 include:

The above items are explained in more detail in the sections below.

Migration to Version 9.4

A dump/restore using pg_dumpall, or use of pg_upgrade, is required for those wishing to migrate data from any previous release.

Version 9.4 contains a number of changes that may affect compatibility with previous releases. Observe the following incompatibilities:

Changes

Below you will find a detailed account of the changes between PostgreSQL 9.4 and the previous major release.

Server

Indexes (PG 9.4.0)

General Performance (PG 9.4.0)

Monitoring (PG 9.4.0)

SSL (PG 9.4.0)

Server Settings (PG 9.4.0)

Replication and Recovery

Logical Decoding (PG 9.4.0)

Logical decoding allows database changes to be streamed in a configurable format. The data is read from the WAL and transformed into the desired target format. To implement this feature, the following changes were made:

Queries

Utility Commands

EXPLAIN (PG 9.4.0)

Views (PG 9.4.0)

Object Manipulation

Data Types

JSON (PG 9.4.0)

Functions

System Information Functions (PG 9.4.0)

Aggregates (PG 9.4.0)

Server-Side Languages

PL/pgSQL Server-Side Language (PG 9.4.0)

libpq

Client Applications

psql (PG 9.4.0)

Backslash Commands (PG 9.4.0)

pg_dump (PG 9.4.0)

pg_basebackup (PG 9.4.0)

Source Code

Additional Modules

pgbench (PG 9.4.0)

pg_stat_statements (PG 9.4.0)

Postgres version 9.3.25 (end of life as of November 8, 2018)

Release date: 2018-11-08

This release contains a variety of fixes from 9.3.24. For information about new features in the 9.3 major release, see Version 9.3.0.

This is expected to be the last PostgreSQL release in the 9.3.X series. Users are encouraged to update to a newer release branch soon.

Migration to Version 9.3.25

A dump/restore is not required for those running 9.3.X.

However, if you are upgrading from a version earlier than 9.3.23, see Version 9.3.23.

Changes

Postgres version 9.3.24 (end of life as of November 8, 2018)

Release date: 2018-08-09

This release contains a variety of fixes from 9.3.23. For information about new features in the 9.3 major release, see Version 9.3.0.

The PostgreSQL community will stop releasing updates for the 9.3.X release series shortly after September 2018. Users are encouraged to update to a newer release branch soon.

Migration to Version 9.3.24

A dump/restore is not required for those running 9.3.X.

However, if you are upgrading from a version earlier than 9.3.23, see Version 9.3.23.

Changes

Postgres version 9.3.23 (end of life as of November 8, 2018)

Release date: 2018-05-10

This release contains a variety of fixes from 9.3.22. For information about new features in the 9.3 major release, see Version 9.3.0.

Migration to Version 9.3.23

A dump/restore is not required for those running 9.3.X.

However, if the function marking mistakes mentioned in the first changelog entry below affect you, you will want to take steps to correct your database catalogs.

Also, if you are upgrading from a version earlier than 9.3.22, see Version 9.3.22.

Changes

Postgres version 9.3.22 (end of life as of November 8, 2018)

Release date: 2018-03-01

This release contains a variety of fixes from 9.3.21. For information about new features in the 9.3 major release, see Version 9.3.0.

Migration to Version 9.3.22

A dump/restore is not required for those running 9.3.X.

However, if you run an installation in which not all users are mutually trusting, or if you maintain an application or extension that is intended for use in arbitrary situations, it is strongly recommended that you read the documentation changes described in the first changelog entry below, and take suitable steps to ensure that your installation or code is secure.

Also, the changes described in the second changelog entry below may cause functions used in index expressions or materialized views to fail during auto-analyze, or when reloading from a dump. After upgrading, monitor the server logs for such problems, and fix affected functions.

Also, if you are upgrading from a version earlier than 9.3.18, see Version 9.3.18.

Changes

Postgres version 9.3.21 (end of life as of November 8, 2018)

Release date: 2018-02-08

This release contains a variety of fixes from 9.3.20. For information about new features in the 9.3 major release, see Version 9.3.0.

Migration to Version 9.3.21

A dump/restore is not required for those running 9.3.X.

However, if you are upgrading from a version earlier than 9.3.18, see Version 9.3.18.

Changes

Postgres version 9.3.20 (end of life as of November 8, 2018)

Release date: 2017-11-09

This release contains a variety of fixes from 9.3.19. For information about new features in the 9.3 major release, see Version 9.3.0.

Migration to Version 9.3.20

A dump/restore is not required for those running 9.3.X.

However, if you are upgrading from a version earlier than 9.3.18, see Version 9.3.18.

Changes

Postgres version 9.3.19 (end of life as of November 8, 2018)

Release date: 2017-08-31

This release contains a small number of fixes from 9.3.18. For information about new features in the 9.3 major release, see Version 9.3.0.

Migration to Version 9.3.19

A dump/restore is not required for those running 9.3.X.

However, if you are upgrading from a version earlier than 9.3.18, see Version 9.3.18.

Changes

Postgres version 9.3.18 (end of life as of November 8, 2018)

Release date: 2017-08-10

This release contains a variety of fixes from 9.3.17. For information about new features in the 9.3 major release, see Version 9.3.0.

Migration to Version 9.3.18

A dump/restore is not required for those running 9.3.X.

However, if you use foreign data servers that make use of user passwords for authentication, see the first changelog entry below.

Also, if you are upgrading from a version earlier than 9.3.16, see Version 9.3.16.

Changes

Postgres version 9.3.17 (end of life as of November 8, 2018)

Release date: 2017-05-11

This release contains a variety of fixes from 9.3.16. For information about new features in the 9.3 major release, see Version 9.3.0.

Migration to Version 9.3.17

A dump/restore is not required for those running 9.3.X.

However, if you use foreign data servers that make use of user passwords for authentication, see the first changelog entry below.

Also, if you are upgrading from a version earlier than 9.3.16, see Version 9.3.16.

Changes

Postgres version 9.3.16 (end of life as of November 8, 2018)

Release date: 2017-02-09

This release contains a variety of fixes from 9.3.15. For information about new features in the 9.3 major release, see Version 9.3.0.

Migration to Version 9.3.16

A dump/restore is not required for those running 9.3.X.

However, if your installation has been affected by the bug described in the first changelog entry below, then after updating you may need to take action to repair corrupted indexes.

Also, if you are upgrading from a version earlier than 9.3.15, see Version 9.3.15.

Changes

Postgres version 9.3.15 (end of life as of November 8, 2018)

Release date: 2016-10-27

This release contains a variety of fixes from 9.3.14. For information about new features in the 9.3 major release, see Version 9.3.0.

Migration to Version 9.3.15

A dump/restore is not required for those running 9.3.X.

However, if your installation has been affected by the bug described in the first changelog entry below, then after updating you may need to take action to repair corrupted free space maps.

Also, if you are upgrading from a version earlier than 9.3.9, see Version 9.3.9.

Changes

Postgres version 9.3.14 (end of life as of November 8, 2018)

Release date: 2016-08-11

This release contains a variety of fixes from 9.3.13. For information about new features in the 9.3 major release, see Version 9.3.0.

Migration to Version 9.3.14

A dump/restore is not required for those running 9.3.X.

However, if you are upgrading from a version earlier than 9.3.9, see Version 9.3.9.

Changes

Postgres version 9.3.13 (end of life as of November 8, 2018)

Release date: 2016-05-12

This release contains a variety of fixes from 9.3.12. For information about new features in the 9.3 major release, see Version 9.3.0.

Migration to Version 9.3.13

A dump/restore is not required for those running 9.3.X.

However, if you are upgrading from a version earlier than 9.3.9, see Version 9.3.9.

Changes

Postgres version 9.3.12 (end of life as of November 8, 2018)

Release date: 2016-03-31

This release contains a variety of fixes from 9.3.11. For information about new features in the 9.3 major release, see Version 9.3.0.

Migration to Version 9.3.12

A dump/restore is not required for those running 9.3.X.

However, if you are upgrading from a version earlier than 9.3.9, see Version 9.3.9.

Changes

Postgres version 9.3.11 (end of life as of November 8, 2018)

Release date: 2016-02-11

This release contains a variety of fixes from 9.3.10. For information about new features in the 9.3 major release, see Version 9.3.0.

Migration to Version 9.3.11

A dump/restore is not required for those running 9.3.X.

However, if you are upgrading from a version earlier than 9.3.9, see Version 9.3.9.

Changes

Postgres version 9.3.10 (end of life as of November 8, 2018)

Release date: 2015-10-08

This release contains a variety of fixes from 9.3.9. For information about new features in the 9.3 major release, see Version 9.3.0.

Migration to Version 9.3.10

A dump/restore is not required for those running 9.3.X.

However, if you are upgrading from a version earlier than 9.3.9, see Version 9.3.9.

Changes

Postgres version 9.3.9 (end of life as of November 8, 2018)

Release date: 2015-06-12

This release contains a small number of fixes from 9.3.8. For information about new features in the 9.3 major release, see Version 9.3.0.

Migration to Version 9.3.9

A dump/restore is not required for those running 9.3.X.

However, if you are upgrading an installation that was previously upgraded using a pg_upgrade version between 9.3.0 and 9.3.4 inclusive, see the first changelog entry below.

Also, if you are upgrading from a version earlier than 9.3.7, see Version 9.3.7.

Changes

Postgres version 9.3.8 (end of life as of November 8, 2018)

Release date: 2015-06-04

This release contains a small number of fixes from 9.3.7. For information about new features in the 9.3 major release, see Version 9.3.0.

Migration to Version 9.3.8

A dump/restore is not required for those running 9.3.X.

However, if you are upgrading from a version earlier than 9.3.7, see Version 9.3.7.

Changes

Postgres version 9.3.7 (end of life as of November 8, 2018)

Release date: 2015-05-22

This release contains a variety of fixes from 9.3.6. For information about new features in the 9.3 major release, see Version 9.3.0.

Migration to Version 9.3.7

A dump/restore is not required for those running 9.3.X.

However, if you use contrib/citext's regexp_matches() functions, see the changelog entry below about that.

Also, if you are upgrading from a version earlier than 9.3.6, see Version 9.3.6.

Changes

Postgres version 9.3.6 (end of life as of November 8, 2018)

Release date: 2015-02-05

This release contains a variety of fixes from 9.3.5. For information about new features in the 9.3 major release, see Version 9.3.0.

Migration to Version 9.3.6

A dump/restore is not required for those running 9.3.X.

However, if you are a Windows user and are using the "Norwegian (BokmĂĽl)" locale, manual action is needed after the upgrade to replace any "Norwegian (BokmĂĽl)_Norway" locale names stored in PostgreSQL system catalogs with the plain-ASCII alias "Norwegian_Norway". For details see http://wiki.postgresql.org/wiki/Changes_To_Norwegian_Locale

Also, if you are upgrading from a version earlier than 9.3.5, see Version 9.3.5.

Changes

Postgres version 9.3.5 (end of life as of November 8, 2018)

Release date: 2014-07-24

This release contains a variety of fixes from 9.3.4. For information about new features in the 9.3 major release, see Version 9.3.0.

Migration to Version 9.3.5

A dump/restore is not required for those running 9.3.X.

However, this release corrects a logic error in pg_upgrade, as well as an index corruption problem in some GiST indexes. See the first two changelog entries below to find out whether your installation has been affected and what steps you should take if so.

Also, if you are upgrading from a version earlier than 9.3.4, see Version 9.3.4.

Changes

Postgres version 9.3.4 (end of life as of November 8, 2018)

Release date: 2014-03-20

This release contains a variety of fixes from 9.3.3. For information about new features in the 9.3 major release, see Version 9.3.0.

Migration to Version 9.3.4

A dump/restore is not required for those running 9.3.X.

However, the error fixed in the first changelog entry below could have resulted in corrupt data on standby servers. It may be prudent to reinitialize standby servers from fresh base backups after installing this update.

Also, if you are upgrading from a version earlier than 9.3.3, see Version 9.3.3.

Changes

Postgres version 9.3.3 (end of life as of November 8, 2018)

Release date: 2014-02-20

This release contains a variety of fixes from 9.3.2. For information about new features in the 9.3 major release, see Version 9.3.0.

Migration to Version 9.3.3

A dump/restore is not required for those running 9.3.X.

However, several of the issues corrected in this release could have resulted in corruption of foreign-key constraints; that is, there might now be referencing rows for which there is no matching row in the referenced table. It may be worthwhile to recheck such constraints after installing this update. The simplest way to do that is to drop and recreate each suspect constraint; however, that will require taking an exclusive lock on both tables, so it is unlikely to be acceptable in production databases. Alternatively, you can do a manual join query between the two tables to look for unmatched rows.

Note also the requirement for replication standby servers to be upgraded before their master server is upgraded.

Also, if you are upgrading from a version earlier than 9.3.2, see Version 9.3.2.

Changes

Postgres version 9.3.2 (end of life as of November 8, 2018)

Release date: 2013-12-05

This release contains a variety of fixes from 9.3.1. For information about new features in the 9.3 major release, see Version 9.3.0.

Migration to Version 9.3.2

A dump/restore is not required for those running 9.3.X.

However, this release corrects a number of potential data corruption issues. See the first three changelog entries below to find out whether your installation has been affected and what steps you can take if so.

Also, if you are upgrading from a version earlier than 9.3.1, see Version 9.3.1.

Changes

Postgres version 9.3.1 (end of life as of November 8, 2018)

Release date: 2013-10-10

This release contains a variety of fixes from 9.3.0. For information about new features in the 9.3 major release, see Version 9.3.0.

Migration to Version 9.3.1

A dump/restore is not required for those running 9.3.X.

However, if you use the hstore extension, see the first changelog entry.

Changes

Postgres version 9.3.0 (end of life as of November 8, 2018)

Release date: 2013-09-09

Overview

Major enhancements in PostgreSQL 9.3 include:

The above items are explained in more detail in the sections below.

Migration to Version 9.3

A dump/restore using pg_dumpall, or use of pg_upgrade, is required for those wishing to migrate data from any previous release.

Version 9.3 contains a number of changes that may affect compatibility with previous releases. Observe the following incompatibilities:

Server Settings

Other

Changes

Below you will find a detailed account of the changes between PostgreSQL 9.3 and the previous major release.

Server

Locking (PG 9.3.0)

Indexes (PG 9.3.0)

Optimizer (PG 9.3.0)

General Performance (PG 9.3.0)

Monitoring (PG 9.3.0)

Authentication (PG 9.3.0)

Server Settings (PG 9.3.0)

Replication and Recovery

Queries

Object Manipulation

ALTER (PG 9.3.0)

VIEWs (PG 9.3.0)

Data Types

JSON (PG 9.3.0)

Functions

Server-Side Languages

PL/pgSQL Server-Side Language (PG 9.3.0)

PL/Python Server-Side Language (PG 9.3.0)

Server Programming Interface (SPI)

Client Applications

psql (PG 9.3.0)

Backslash Commands (PG 9.3.0)

Output (PG 9.3.0)

pg_dump (PG 9.3.0)

initdb (PG 9.3.0)

Source Code

Additional Modules

pg_upgrade (PG 9.3.0)

pgbench (PG 9.3.0)

Documentation

Postgres version 9.2.24 (end of life as of November 9, 2017)

Release date: 2017-11-09

This release contains a variety of fixes from 9.2.23. For information about new features in the 9.2 major release, see Version 9.2.0.

This is expected to be the last PostgreSQL release in the 9.2.X series. Users are encouraged to update to a newer release branch soon.

Migration to Version 9.2.24

A dump/restore is not required for those running 9.2.X.

However, if you are upgrading from a version earlier than 9.2.22, see Version 9.2.22.

Changes

Postgres version 9.2.23 (end of life as of November 9, 2017)

Release date: 2017-08-31

This release contains a small number of fixes from 9.2.22. For information about new features in the 9.2 major release, see Version 9.2.0.

The PostgreSQL community will stop releasing updates for the 9.2.X release series in September 2017. Users are encouraged to update to a newer release branch soon.

Migration to Version 9.2.23

A dump/restore is not required for those running 9.2.X.

However, if you are upgrading from a version earlier than 9.2.22, see Version 9.2.22.

Changes

Postgres version 9.2.22 (end of life as of November 9, 2017)

Release date: 2017-08-10

This release contains a variety of fixes from 9.2.21. For information about new features in the 9.2 major release, see Version 9.2.0.

The PostgreSQL community will stop releasing updates for the 9.2.X release series in September 2017. Users are encouraged to update to a newer release branch soon.

Migration to Version 9.2.22

A dump/restore is not required for those running 9.2.X.

However, if you use foreign data servers that make use of user passwords for authentication, see the first changelog entry below.

Also, if you are upgrading from a version earlier than 9.2.20, see Version 9.2.20.

Changes

Postgres version 9.2.21 (end of life as of November 9, 2017)

Release date: 2017-05-11

This release contains a variety of fixes from 9.2.20. For information about new features in the 9.2 major release, see Version 9.2.0.

The PostgreSQL community will stop releasing updates for the 9.2.X release series in September 2017. Users are encouraged to update to a newer release branch soon.

Migration to Version 9.2.21

A dump/restore is not required for those running 9.2.X.

However, if you use foreign data servers that make use of user passwords for authentication, see the first changelog entry below.

Also, if you are upgrading from a version earlier than 9.2.20, see Version 9.2.20.

Changes

Postgres version 9.2.20 (end of life as of November 9, 2017)

Release date: 2017-02-09

This release contains a variety of fixes from 9.2.19. For information about new features in the 9.2 major release, see Version 9.2.0.

Migration to Version 9.2.20

A dump/restore is not required for those running 9.2.X.

However, if your installation has been affected by the bug described in the first changelog entry below, then after updating you may need to take action to repair corrupted indexes.

Also, if you are upgrading from a version earlier than 9.2.11, see Version 9.2.11.

Changes

Postgres version 9.2.19 (end of life as of November 9, 2017)

Release date: 2016-10-27

This release contains a variety of fixes from 9.2.18. For information about new features in the 9.2 major release, see Version 9.2.0.

Migration to Version 9.2.19

A dump/restore is not required for those running 9.2.X.

However, if you are upgrading from a version earlier than 9.2.11, see Version 9.2.11.

Changes

Postgres version 9.2.18 (end of life as of November 9, 2017)

Release date: 2016-08-11

This release contains a variety of fixes from 9.2.17. For information about new features in the 9.2 major release, see Version 9.2.0.

Migration to Version 9.2.18

A dump/restore is not required for those running 9.2.X.

However, if you are upgrading from a version earlier than 9.2.11, see Version 9.2.11.

Changes

Postgres version 9.2.17 (end of life as of November 9, 2017)

Release date: 2016-05-12

This release contains a variety of fixes from 9.2.16. For information about new features in the 9.2 major release, see Version 9.2.0.

Migration to Version 9.2.17

A dump/restore is not required for those running 9.2.X.

However, if you are upgrading from a version earlier than 9.2.11, see Version 9.2.11.

Changes

Postgres version 9.2.16 (end of life as of November 9, 2017)

Release date: 2016-03-31

This release contains a variety of fixes from 9.2.15. For information about new features in the 9.2 major release, see Version 9.2.0.

Migration to Version 9.2.16

A dump/restore is not required for those running 9.2.X.

However, if you are upgrading from a version earlier than 9.2.11, see Version 9.2.11.

Changes

Postgres version 9.2.15 (end of life as of November 9, 2017)

Release date: 2016-02-11

This release contains a variety of fixes from 9.2.14. For information about new features in the 9.2 major release, see Version 9.2.0.

Migration to Version 9.2.15

A dump/restore is not required for those running 9.2.X.

However, if you are upgrading from a version earlier than 9.2.11, see Version 9.2.11.

Changes

Postgres version 9.2.14 (end of life as of November 9, 2017)

Release date: 2015-10-08

This release contains a variety of fixes from 9.2.13. For information about new features in the 9.2 major release, see Version 9.2.0.

Migration to Version 9.2.14

A dump/restore is not required for those running 9.2.X.

However, if you are upgrading from a version earlier than 9.2.11, see Version 9.2.11.

Changes

Postgres version 9.2.13 (end of life as of November 9, 2017)

Release date: 2015-06-12

This release contains a small number of fixes from 9.2.12. For information about new features in the 9.2 major release, see Version 9.2.0.

Migration to Version 9.2.13

A dump/restore is not required for those running 9.2.X.

However, if you are upgrading from a version earlier than 9.2.11, see Version 9.2.11.

Changes

Postgres version 9.2.12 (end of life as of November 9, 2017)

Release date: 2015-06-04

This release contains a small number of fixes from 9.2.11. For information about new features in the 9.2 major release, see Version 9.2.0.

Migration to Version 9.2.12

A dump/restore is not required for those running 9.2.X.

However, if you are upgrading from a version earlier than 9.2.11, see Version 9.2.11.

Changes

Postgres version 9.2.11 (end of life as of November 9, 2017)

Release date: 2015-05-22

This release contains a variety of fixes from 9.2.10. For information about new features in the 9.2 major release, see Version 9.2.0.

Migration to Version 9.2.11

A dump/restore is not required for those running 9.2.X.

However, if you use contrib/citext's regexp_matches() functions, see the changelog entry below about that.

Also, if you are upgrading from a version earlier than 9.2.10, see Version 9.2.10.

Changes

Postgres version 9.2.10 (end of life as of November 9, 2017)

Release date: 2015-02-05

This release contains a variety of fixes from 9.2.9. For information about new features in the 9.2 major release, see Version 9.2.0.

Migration to Version 9.2.10

A dump/restore is not required for those running 9.2.X.

However, if you are a Windows user and are using the "Norwegian (BokmĂĽl)" locale, manual action is needed after the upgrade to replace any "Norwegian (BokmĂĽl)_Norway" locale names stored in PostgreSQL system catalogs with the plain-ASCII alias "Norwegian_Norway". For details see http://wiki.postgresql.org/wiki/Changes_To_Norwegian_Locale

Also, if you are upgrading from a version earlier than 9.2.9, see Version 9.2.9.

Changes

Postgres version 9.2.9 (end of life as of November 9, 2017)

Release date: 2014-07-24

This release contains a variety of fixes from 9.2.8. For information about new features in the 9.2 major release, see Version 9.2.0.

Migration to Version 9.2.9

A dump/restore is not required for those running 9.2.X.

However, this release corrects an index corruption problem in some GiST indexes. See the first changelog entry below to find out whether your installation has been affected and what steps you should take if so.

Also, if you are upgrading from a version earlier than 9.2.6, see Version 9.2.6.

Changes

Postgres version 9.2.8 (end of life as of November 9, 2017)

Release date: 2014-03-20

This release contains a variety of fixes from 9.2.7. For information about new features in the 9.2 major release, see Version 9.2.0.

Migration to Version 9.2.8

A dump/restore is not required for those running 9.2.X.

However, if you are upgrading from a version earlier than 9.2.6, see Version 9.2.6.

Changes

Postgres version 9.2.7 (end of life as of November 9, 2017)

Release date: 2014-02-20

This release contains a variety of fixes from 9.2.6. For information about new features in the 9.2 major release, see Version 9.2.0.

Migration to Version 9.2.7

A dump/restore is not required for those running 9.2.X.

However, if you are upgrading from a version earlier than 9.2.6, see Version 9.2.6.

Changes

Postgres version 9.2.6 (end of life as of November 9, 2017)

Release date: 2013-12-05

This release contains a variety of fixes from 9.2.5. For information about new features in the 9.2 major release, see Version 9.2.0.

Migration to Version 9.2.6

A dump/restore is not required for those running 9.2.X.

However, this release corrects a number of potential data corruption issues. See the first two changelog entries below to find out whether your installation has been affected and what steps you can take if so.

Also, if you are upgrading from a version earlier than 9.2.4, see Version 9.2.4.

Changes

Postgres version 9.2.5 (end of life as of November 9, 2017)

Release date: 2013-10-10

This release contains a variety of fixes from 9.2.4. For information about new features in the 9.2 major release, see Version 9.2.0.

Migration to Version 9.2.5

A dump/restore is not required for those running 9.2.X.

However, if you are upgrading from a version earlier than 9.2.4, see Version 9.2.4.

Changes

Postgres version 9.2.4 (end of life as of November 9, 2017)

Release date: 2013-04-04

This release contains a variety of fixes from 9.2.3. For information about new features in the 9.2 major release, see Version 9.2.0.

Migration to Version 9.2.4

A dump/restore is not required for those running 9.2.X.

However, this release corrects several errors in management of GiST indexes. After installing this update, it is advisable to REINDEX any GiST indexes that meet one or more of the conditions described below.

Also, if you are upgrading from a version earlier than 9.2.2, see Version 9.2.2.

Changes

Postgres version 9.2.3 (end of life as of November 9, 2017)

Release date: 2013-02-07

This release contains a variety of fixes from 9.2.2. For information about new features in the 9.2 major release, see Version 9.2.0.

Migration to Version 9.2.3

A dump/restore is not required for those running 9.2.X.

However, if you are upgrading from a version earlier than 9.2.2, see Version 9.2.2.

Changes

Postgres version 9.2.2 (end of life as of November 9, 2017)

Release date: 2012-12-06

This release contains a variety of fixes from 9.2.1. For information about new features in the 9.2 major release, see Version 9.2.0.

Migration to Version 9.2.2

A dump/restore is not required for those running 9.2.X.

However, you may need to perform REINDEX operations to correct problems in concurrently-built indexes, as described in the first changelog item below.

Also, if you are upgrading from version 9.2.0, see Version 9.2.1.

Changes

Postgres version 9.2.1 (end of life as of November 9, 2017)

Release date: 2012-09-24

This release contains a variety of fixes from 9.2.0. For information about new features in the 9.2 major release, see Version 9.2.0.

Migration to Version 9.2.1

A dump/restore is not required for those running 9.2.X.

However, you may need to perform REINDEX and/or VACUUM operations to recover from the effects of the data corruption bug described in the first changelog item below.

Changes

Postgres version 9.2.0 (end of life as of November 9, 2017)

Release date: 2012-09-10

Overview

This release has been largely focused on performance improvements, though new SQL features are not lacking. Work also continues in the area of replication support. Major enhancements include:

The above items are explained in more detail in the sections below.

Migration to Version 9.2

A dump/restore using pg_dump, or use of pg_upgrade, is required for those wishing to migrate data from any previous release.

Version 9.2 contains a number of changes that may affect compatibility with previous releases. Observe the following incompatibilities:

System Catalogs

Functions

Object Modification

Command-Line Tools

Server Settings

Monitoring

Changes

Below you will find a detailed account of the changes between PostgreSQL 9.2 and the previous major release.

Server

Performance (PG 9.2.0)

Process Management (PG 9.2.0)

Optimizer (PG 9.2.0)

Authentication (PG 9.2.0)

Monitoring (PG 9.2.0)

Statistical Views (PG 9.2.0)

Server Settings (PG 9.2.0)

postgresql.conf (PG 9.2.0)

Replication and Recovery

Queries

Object Manipulation

Constraints (PG 9.2.0)

ALTER (PG 9.2.0)

CREATE TABLE (PG 9.2.0)

Object Permissions (PG 9.2.0)

Utility Operations

Data Types

Functions

Information Schema

Server-Side Languages

PL/pgSQL Server-Side Language (PG 9.2.0)

PL/Python Server-Side Language (PG 9.2.0)

SQL Server-Side Language (PG 9.2.0)

Client Applications

psql (PG 9.2.0)

Informational Commands (PG 9.2.0)

Tab Completion (PG 9.2.0)

pg_dump (PG 9.2.0)

libpq

Source Code

Additional Modules

pg_upgrade (PG 9.2.0)

pg_stat_statements (PG 9.2.0)

sepgsql (PG 9.2.0)

Documentation

Postgres version 9.1.24 (end of life as of October 27, 2016)

Release date: 2016-10-27

This release contains a variety of fixes from 9.1.23. For information about new features in the 9.1 major release, see Version 9.1.0.

This is expected to be the last PostgreSQL release in the 9.1.X series. Users are encouraged to update to a newer release branch soon.

Migration to Version 9.1.24

A dump/restore is not required for those running 9.1.X.

However, if you are upgrading from a version earlier than 9.1.16, see Version 9.1.16.

Changes

Postgres version 9.1.23 (end of life as of October 27, 2016)

Release date: 2016-08-11

This release contains a variety of fixes from 9.1.22. For information about new features in the 9.1 major release, see Version 9.1.0.

The PostgreSQL community will stop releasing updates for the 9.1.X release series in September 2016. Users are encouraged to update to a newer release branch soon.

Migration to Version 9.1.23

A dump/restore is not required for those running 9.1.X.

However, if you are upgrading from a version earlier than 9.1.16, see Version 9.1.16.

Changes

Postgres version 9.1.22 (end of life as of October 27, 2016)

Release date: 2016-05-12

This release contains a variety of fixes from 9.1.21. For information about new features in the 9.1 major release, see Version 9.1.0.

The PostgreSQL community will stop releasing updates for the 9.1.X release series in September 2016. Users are encouraged to update to a newer release branch soon.

Migration to Version 9.1.22

A dump/restore is not required for those running 9.1.X.

However, if you are upgrading from a version earlier than 9.1.16, see Version 9.1.16.

Changes

Postgres version 9.1.21 (end of life as of October 27, 2016)

Release date: 2016-03-31

This release contains a variety of fixes from 9.1.20. For information about new features in the 9.1 major release, see Version 9.1.0.

Migration to Version 9.1.21

A dump/restore is not required for those running 9.1.X.

However, if you are upgrading from a version earlier than 9.1.16, see Version 9.1.16.

Changes

Postgres version 9.1.20 (end of life as of October 27, 2016)

Release date: 2016-02-11

This release contains a variety of fixes from 9.1.19. For information about new features in the 9.1 major release, see Version 9.1.0.

Migration to Version 9.1.20

A dump/restore is not required for those running 9.1.X.

However, if you are upgrading from a version earlier than 9.1.16, see Version 9.1.16.

Changes

Postgres version 9.1.19 (end of life as of October 27, 2016)

Release date: 2015-10-08

This release contains a variety of fixes from 9.1.18. For information about new features in the 9.1 major release, see Version 9.1.0.

Migration to Version 9.1.19

A dump/restore is not required for those running 9.1.X.

However, if you are upgrading from a version earlier than 9.1.16, see Version 9.1.16.

Changes

Postgres version 9.1.18 (end of life as of October 27, 2016)

Release date: 2015-06-12

This release contains a small number of fixes from 9.1.17. For information about new features in the 9.1 major release, see Version 9.1.0.

Migration to Version 9.1.18

A dump/restore is not required for those running 9.1.X.

However, if you are upgrading from a version earlier than 9.1.16, see Version 9.1.16.

Changes

Postgres version 9.1.17 (end of life as of October 27, 2016)

Release date: 2015-06-04

This release contains a small number of fixes from 9.1.16. For information about new features in the 9.1 major release, see Version 9.1.0.

Migration to Version 9.1.17

A dump/restore is not required for those running 9.1.X.

However, if you are upgrading from a version earlier than 9.1.16, see Version 9.1.16.

Changes

Postgres version 9.1.16 (end of life as of October 27, 2016)

Release date: 2015-05-22

This release contains a variety of fixes from 9.1.15. For information about new features in the 9.1 major release, see Version 9.1.0.

Migration to Version 9.1.16

A dump/restore is not required for those running 9.1.X.

However, if you use contrib/citext's regexp_matches() functions, see the changelog entry below about that.

Also, if you are upgrading from a version earlier than 9.1.14, see Version 9.1.14.

Changes

Postgres version 9.1.15 (end of life as of October 27, 2016)

Release date: 2015-02-05

This release contains a variety of fixes from 9.1.14. For information about new features in the 9.1 major release, see Version 9.1.0.

Migration to Version 9.1.15

A dump/restore is not required for those running 9.1.X.

However, if you are upgrading from a version earlier than 9.1.14, see Version 9.1.14.

Changes

Postgres version 9.1.14 (end of life as of October 27, 2016)

Release date: 2014-07-24

This release contains a variety of fixes from 9.1.13. For information about new features in the 9.1 major release, see Version 9.1.0.

Migration to Version 9.1.14

A dump/restore is not required for those running 9.1.X.

However, this release corrects an index corruption problem in some GiST indexes. See the first changelog entry below to find out whether your installation has been affected and what steps you should take if so.

Also, if you are upgrading from a version earlier than 9.1.11, see Version 9.1.11.

Changes

Postgres version 9.1.13 (end of life as of October 27, 2016)

Release date: 2014-03-20

This release contains a variety of fixes from 9.1.12. For information about new features in the 9.1 major release, see Version 9.1.0.

Migration to Version 9.1.13

A dump/restore is not required for those running 9.1.X.

However, if you are upgrading from a version earlier than 9.1.11, see Version 9.1.11.

Changes

Postgres version 9.1.12 (end of life as of October 27, 2016)

Release date: 2014-02-20

This release contains a variety of fixes from 9.1.11. For information about new features in the 9.1 major release, see Version 9.1.0.

Migration to Version 9.1.12

A dump/restore is not required for those running 9.1.X.

However, if you are upgrading from a version earlier than 9.1.11, see Version 9.1.11.

Changes

Postgres version 9.1.11 (end of life as of October 27, 2016)

Release date: 2013-12-05

This release contains a variety of fixes from 9.1.10. For information about new features in the 9.1 major release, see Version 9.1.0.

Migration to Version 9.1.11

A dump/restore is not required for those running 9.1.X.

However, this release corrects a number of potential data corruption issues. See the first two changelog entries below to find out whether your installation has been affected and what steps you can take if so.

Also, if you are upgrading from a version earlier than 9.1.9, see Version 9.1.9.

Changes

Postgres version 9.1.10 (end of life as of October 27, 2016)

Release date: 2013-10-10

This release contains a variety of fixes from 9.1.9. For information about new features in the 9.1 major release, see Version 9.1.0.

Migration to Version 9.1.10

A dump/restore is not required for those running 9.1.X.

However, if you are upgrading from a version earlier than 9.1.9, see Version 9.1.9.

Changes

Postgres version 9.1.9 (end of life as of October 27, 2016)

Release date: 2013-04-04

This release contains a variety of fixes from 9.1.8. For information about new features in the 9.1 major release, see Version 9.1.0.

Migration to Version 9.1.9

A dump/restore is not required for those running 9.1.X.

However, this release corrects several errors in management of GiST indexes. After installing this update, it is advisable to REINDEX any GiST indexes that meet one or more of the conditions described below.

Also, if you are upgrading from a version earlier than 9.1.6, see Version 9.1.6.

Changes

Postgres version 9.1.8 (end of life as of October 27, 2016)

Release date: 2013-02-07

This release contains a variety of fixes from 9.1.7. For information about new features in the 9.1 major release, see Version 9.1.0.

Migration to Version 9.1.8

A dump/restore is not required for those running 9.1.X.

However, if you are upgrading from a version earlier than 9.1.6, see Version 9.1.6.

Changes

Postgres version 9.1.7 (end of life as of October 27, 2016)

Release date: 2012-12-06

This release contains a variety of fixes from 9.1.6. For information about new features in the 9.1 major release, see Version 9.1.0.

Migration to Version 9.1.7

A dump/restore is not required for those running 9.1.X.

However, if you are upgrading from a version earlier than 9.1.6, see Version 9.1.6.

Changes

Postgres version 9.1.6 (end of life as of October 27, 2016)

Release date: 2012-09-24

This release contains a variety of fixes from 9.1.5. For information about new features in the 9.1 major release, see Version 9.1.0.

Migration to Version 9.1.6

A dump/restore is not required for those running 9.1.X.

However, you may need to perform REINDEX operations to recover from the effects of the data corruption bug described in the first changelog item below.

Also, if you are upgrading from a version earlier than 9.1.4, see Version 9.1.4.

Changes

Postgres version 9.1.5 (end of life as of October 27, 2016)

Release date: 2012-08-17

This release contains a variety of fixes from 9.1.4. For information about new features in the 9.1 major release, see Version 9.1.0.

Migration to Version 9.1.5

A dump/restore is not required for those running 9.1.X.

However, if you are upgrading from a version earlier than 9.1.4, see Version 9.1.4.

Changes

Postgres version 9.1.4 (end of life as of October 27, 2016)

Release date: 2012-06-04

This release contains a variety of fixes from 9.1.3. For information about new features in the 9.1 major release, see Version 9.1.0.

Migration to Version 9.1.4

A dump/restore is not required for those running 9.1.X.

However, if you use the citext data type, and you upgraded from a previous major release by running pg_upgrade, you should run CREATE EXTENSION citext FROM unpackaged to avoid collation-related failures in citext operations. The same is necessary if you restore a dump from a pre-9.1 database that contains an instance of the citext data type. If you've already run the CREATE EXTENSION command before upgrading to 9.1.4, you will instead need to do manual catalog updates as explained in the third changelog item below.

Also, if you are upgrading from a version earlier than 9.1.2, see Version 9.1.2.

Changes

Postgres version 9.1.3 (end of life as of October 27, 2016)

Release date: 2012-02-27

This release contains a variety of fixes from 9.1.2. For information about new features in the 9.1 major release, see Version 9.1.0.

Migration to Version 9.1.3

A dump/restore is not required for those running 9.1.X.

However, if you are upgrading from a version earlier than 9.1.2, see Version 9.1.2.

Changes

Postgres version 9.1.2 (end of life as of October 27, 2016)

Release date: 2011-12-05

This release contains a variety of fixes from 9.1.1. For information about new features in the 9.1 major release, see Version 9.1.0.

Migration to Version 9.1.2

A dump/restore is not required for those running 9.1.X.

However, a longstanding error was discovered in the definition of the information_schema.referential_constraints view. If you rely on correct results from that view, you should replace its definition as explained in the first changelog item below.

Also, if you use the citext data type, and you upgraded from a previous major release by running pg_upgrade, you should run CREATE EXTENSION citext FROM unpackaged to avoid collation-related failures in citext operations. The same is necessary if you restore a dump from a pre-9.1 database that contains an instance of the citext data type. If you've already run the CREATE EXTENSION command before upgrading to 9.1.2, you will instead need to do manual catalog updates as explained in the second changelog item.

Changes

Postgres version 9.1.1 (end of life as of October 27, 2016)

Release date: 2011-09-26

This release contains a small number of fixes from 9.1.0. For information about new features in the 9.1 major release, see Version 9.1.0.

Migration to Version 9.1.1

A dump/restore is not required for those running 9.1.X.

Changes

Postgres version 9.1.0 (end of life as of October 27, 2016)

Release date: 2011-09-12

Overview

This release shows PostgreSQL moving beyond the traditional relational-database feature set with new, ground-breaking functionality that is unique to PostgreSQL. The streaming replication feature introduced in release 9.0 is significantly enhanced by adding a synchronous-replication option, streaming backups, and monitoring improvements. Major enhancements include:

The above items are explained in more detail in the sections below.

Migration to Version 9.1

A dump/restore using pg_dump, or use of pg_upgrade, is required for those wishing to migrate data from any previous release.

Version 9.1 contains a number of changes that may affect compatibility with previous releases. Observe the following incompatibilities:

Strings

Casting

Arrays

Object Modification

Server Settings

PL/pgSQL Server-Side Language

Contrib

Other Incompatibilities

Changes

Below you will find a detailed account of the changes between PostgreSQL 9.1 and the previous major release.

Server

Performance (PG 9.1.0)

Optimizer (PG 9.1.0)

Authentication (PG 9.1.0)

Monitoring (PG 9.1.0)

Statistical Views (PG 9.1.0)

Server Settings (PG 9.1.0)

Replication and Recovery

Streaming Replication and Continuous Archiving (PG 9.1.0)

Replication Monitoring (PG 9.1.0)

Hot Standby (PG 9.1.0)

Recovery Control (PG 9.1.0)

Queries

Strings (PG 9.1.0)

Object Manipulation

ALTER Object (PG 9.1.0)

CREATE/ALTER TABLE (PG 9.1.0)

Object Permissions (PG 9.1.0)

Utility Operations

COPY (PG 9.1.0)

EXPLAIN (PG 9.1.0)

VACUUM (PG 9.1.0)

CLUSTER (PG 9.1.0)

Indexes (PG 9.1.0)

Data Types

Casting (PG 9.1.0)

XML (PG 9.1.0)

Functions

Object Information Functions (PG 9.1.0)

Function and Trigger Creation (PG 9.1.0)

Server-Side Languages

PL/pgSQL Server-Side Language (PG 9.1.0)

PL/Perl Server-Side Language (PG 9.1.0)

PL/Python Server-Side Language (PG 9.1.0)

Client Applications

psql (PG 9.1.0)

pg_dump (PG 9.1.0)

pg_ctl (PG 9.1.0)

Development Tools

libpq (PG 9.1.0)

ECPG (PG 9.1.0)

Build Options

Makefiles (PG 9.1.0)

Windows (PG 9.1.0)

Source Code

Server Hooks (PG 9.1.0)

Contrib

Security (PG 9.1.0)

Performance (PG 9.1.0)

Fsync Testing (PG 9.1.0)

Documentation

Postgres version 9.0.23 (end of life as of October 8, 2015)

Release date: 2015-10-08

This release contains a variety of fixes from 9.0.22. For information about new features in the 9.0 major release, see Version 9.0.0.

This is expected to be the last PostgreSQL release in the 9.0.X series. Users are encouraged to update to a newer release branch soon.

Migration to Version 9.0.23

A dump/restore is not required for those running 9.0.X.

However, if you are upgrading from a version earlier than 9.0.18, see Version 9.0.18.

Changes

Postgres version 9.0.22 (end of life as of October 8, 2015)

Release date: 2015-06-12

This release contains a small number of fixes from 9.0.21. For information about new features in the 9.0 major release, see Version 9.0.0.

The PostgreSQL community will stop releasing updates for the 9.0.X release series in September 2015. Users are encouraged to update to a newer release branch soon.

Migration to Version 9.0.22

A dump/restore is not required for those running 9.0.X.

However, if you are upgrading from a version earlier than 9.0.18, see Version 9.0.18.

Changes

Postgres version 9.0.21 (end of life as of October 8, 2015)

Release date: 2015-06-04

This release contains a small number of fixes from 9.0.20. For information about new features in the 9.0 major release, see Version 9.0.0.

The PostgreSQL community will stop releasing updates for the 9.0.X release series in September 2015. Users are encouraged to update to a newer release branch soon.

Migration to Version 9.0.21

A dump/restore is not required for those running 9.0.X.

However, if you are upgrading from a version earlier than 9.0.18, see Version 9.0.18.

Changes

Postgres version 9.0.20 (end of life as of October 8, 2015)

Release date: 2015-05-22

This release contains a variety of fixes from 9.0.19. For information about new features in the 9.0 major release, see Version 9.0.0.

The PostgreSQL community will stop releasing updates for the 9.0.X release series in September 2015. Users are encouraged to update to a newer release branch soon.

Migration to Version 9.0.20

A dump/restore is not required for those running 9.0.X.

However, if you are upgrading from a version earlier than 9.0.18, see Version 9.0.18.

Changes

Postgres version 9.0.19 (end of life as of October 8, 2015)

Release date: 2015-02-05

This release contains a variety of fixes from 9.0.18. For information about new features in the 9.0 major release, see Version 9.0.0.

Migration to Version 9.0.19

A dump/restore is not required for those running 9.0.X.

However, if you are upgrading from a version earlier than 9.0.18, see Version 9.0.18.

Changes

Postgres version 9.0.18 (end of life as of October 8, 2015)

Release date: 2014-07-24

This release contains a variety of fixes from 9.0.17. For information about new features in the 9.0 major release, see Version 9.0.0.

Migration to Version 9.0.18

A dump/restore is not required for those running 9.0.X.

However, this release corrects an index corruption problem in some GiST indexes. See the first changelog entry below to find out whether your installation has been affected and what steps you should take if so.

Also, if you are upgrading from a version earlier than 9.0.15, see Version 9.0.15.

Changes

Postgres version 9.0.17 (end of life as of October 8, 2015)

Release date: 2014-03-20

This release contains a variety of fixes from 9.0.16. For information about new features in the 9.0 major release, see Version 9.0.0.

Migration to Version 9.0.17

A dump/restore is not required for those running 9.0.X.

However, if you are upgrading from a version earlier than 9.0.15, see Version 9.0.15.

Changes

Postgres version 9.0.16 (end of life as of October 8, 2015)

Release date: 2014-02-20

This release contains a variety of fixes from 9.0.15. For information about new features in the 9.0 major release, see Version 9.0.0.

Migration to Version 9.0.16

A dump/restore is not required for those running 9.0.X.

However, if you are upgrading from a version earlier than 9.0.15, see Version 9.0.15.

Changes

Postgres version 9.0.15 (end of life as of October 8, 2015)

Release date: 2013-12-05

This release contains a variety of fixes from 9.0.14. For information about new features in the 9.0 major release, see Version 9.0.0.

Migration to Version 9.0.15

A dump/restore is not required for those running 9.0.X.

However, this release corrects a number of potential data corruption issues. See the first two changelog entries below to find out whether your installation has been affected and what steps you can take if so.

Also, if you are upgrading from a version earlier than 9.0.13, see Version 9.0.13.

Changes

Postgres version 9.0.14 (end of life as of October 8, 2015)

Release date: 2013-10-10

This release contains a variety of fixes from 9.0.13. For information about new features in the 9.0 major release, see Version 9.0.0.

Migration to Version 9.0.14

A dump/restore is not required for those running 9.0.X.

However, if you are upgrading from a version earlier than 9.0.13, see Version 9.0.13.

Changes

Postgres version 9.0.13 (end of life as of October 8, 2015)

Release date: 2013-04-04

This release contains a variety of fixes from 9.0.12. For information about new features in the 9.0 major release, see Version 9.0.0.

Migration to Version 9.0.13

A dump/restore is not required for those running 9.0.X.

However, this release corrects several errors in management of GiST indexes. After installing this update, it is advisable to REINDEX any GiST indexes that meet one or more of the conditions described below.

Also, if you are upgrading from a version earlier than 9.0.6, see Version 9.0.6.

Changes

Postgres version 9.0.12 (end of life as of October 8, 2015)

Release date: 2013-02-07

This release contains a variety of fixes from 9.0.11. For information about new features in the 9.0 major release, see Version 9.0.0.

Migration to Version 9.0.12

A dump/restore is not required for those running 9.0.X.

However, if you are upgrading from a version earlier than 9.0.6, see Version 9.0.6.

Changes

Postgres version 9.0.11 (end of life as of October 8, 2015)

Release date: 2012-12-06

This release contains a variety of fixes from 9.0.10. For information about new features in the 9.0 major release, see Version 9.0.0.

Migration to Version 9.0.11

A dump/restore is not required for those running 9.0.X.

However, if you are upgrading from a version earlier than 9.0.6, see Version 9.0.6.

Changes

Postgres version 9.0.10 (end of life as of October 8, 2015)

Release date: 2012-09-24

This release contains a variety of fixes from 9.0.9. For information about new features in the 9.0 major release, see Version 9.0.0.

Migration to Version 9.0.10

A dump/restore is not required for those running 9.0.X.

However, if you are upgrading from a version earlier than 9.0.6, see Version 9.0.6.

Changes

Postgres version 9.0.9 (end of life as of October 8, 2015)

Release date: 2012-08-17

This release contains a variety of fixes from 9.0.8. For information about new features in the 9.0 major release, see Version 9.0.0.

Migration to Version 9.0.9

A dump/restore is not required for those running 9.0.X.

However, if you are upgrading from a version earlier than 9.0.6, see Version 9.0.6.

Changes

Postgres version 9.0.8 (end of life as of October 8, 2015)

Release date: 2012-06-04

This release contains a variety of fixes from 9.0.7. For information about new features in the 9.0 major release, see Version 9.0.0.

Migration to Version 9.0.8

A dump/restore is not required for those running 9.0.X.

However, if you are upgrading from a version earlier than 9.0.6, see Version 9.0.6.

Changes

Postgres version 9.0.7 (end of life as of October 8, 2015)

Release date: 2012-02-27

This release contains a variety of fixes from 9.0.6. For information about new features in the 9.0 major release, see Version 9.0.0.

Migration to Version 9.0.7

A dump/restore is not required for those running 9.0.X.

However, if you are upgrading from a version earlier than 9.0.6, see Version 9.0.6.

Changes

Postgres version 9.0.6 (end of life as of October 8, 2015)

Release date: 2011-12-05

This release contains a variety of fixes from 9.0.5. For information about new features in the 9.0 major release, see Version 9.0.0.

Migration to Version 9.0.6

A dump/restore is not required for those running 9.0.X.

However, a longstanding error was discovered in the definition of the information_schema.referential_constraints view. If you rely on correct results from that view, you should replace its definition as explained in the first changelog item below.

Also, if you are upgrading from a version earlier than 9.0.4, see Version 9.0.4.

Changes

Postgres version 9.0.5 (end of life as of October 8, 2015)

Release date: 2011-09-26

This release contains a variety of fixes from 9.0.4. For information about new features in the 9.0 major release, see Version 9.0.0.

Migration to Version 9.0.5

A dump/restore is not required for those running 9.0.X.

However, if you are upgrading from a version earlier than 9.0.4, see Version 9.0.4.

Changes

Postgres version 9.0.4 (end of life as of October 8, 2015)

Release date: 2011-04-18

This release contains a variety of fixes from 9.0.3. For information about new features in the 9.0 major release, see Version 9.0.0.

Migration to Version 9.0.4

A dump/restore is not required for those running 9.0.X.

However, if your installation was upgraded from a previous major release by running pg_upgrade, you should take action to prevent possible data loss due to a now-fixed bug in pg_upgrade. The recommended solution is to run VACUUM FREEZE on all TOAST tables. More information is available at http://wiki.postgresql.org/wiki/20110408pg_upgrade_fix.

Changes

Postgres version 9.0.3 (end of life as of October 8, 2015)

Release date: 2011-01-31

This release contains a variety of fixes from 9.0.2. For information about new features in the 9.0 major release, see Version 9.0.0.

Migration to Version 9.0.3

A dump/restore is not required for those running 9.0.X.

Changes

Postgres version 9.0.2 (end of life as of October 8, 2015)

Release date: 2010-12-16

This release contains a variety of fixes from 9.0.1. For information about new features in the 9.0 major release, see Version 9.0.0.

Migration to Version 9.0.2

A dump/restore is not required for those running 9.0.X.

Changes

Postgres version 9.0.1 (end of life as of October 8, 2015)

Release date: 2010-10-04

This release contains a variety of fixes from 9.0.0. For information about new features in the 9.0 major release, see Version 9.0.0.

Migration to Version 9.0.1

A dump/restore is not required for those running 9.0.X.

Changes

Postgres version 9.0.0 (end of life as of October 8, 2015)

Release date: 2010-09-20

Overview

This release of PostgreSQL adds features that have been requested for years, such as easy-to-use replication, a mass permission-changing facility, and anonymous code blocks. While past major releases have been conservative in their scope, this release shows a bold new desire to provide facilities that new and existing users of PostgreSQL will embrace. This has all been done with few incompatibilities. Major enhancements include:

The above items are explained in more detail in the sections below.

Migration to Version 9.0

A dump/restore using pg_dump, or use of pg_upgrade, is required for those wishing to migrate data from any previous release.

Version 9.0 contains a number of changes that selectively break backwards compatibility in order to support new features and code quality improvements. In particular, users who make extensive use of PL/pgSQL, Point-In-Time Recovery (PITR), or Warm Standby should test their applications because of slight user-visible changes in those areas. Observe the following incompatibilities:

Server Settings

Queries