PostgreSQL 15 Beta 2 release

Hi, The RMT[1] with the release team has set a date of June 30, 2022 for the PostgreSQL 15 Beta 2 release. We encourage you to try to close as many open items[2] prior to the release. If you are working on patches for Beta 2, please be sure that they are committed no later than June 26, 2022

PostgreSQL 15 beta 2 release announcement draft

Hi, Attached is a draft of the release announcement for PostgreSQL 15 Beta 2. Please provide feedback on technical accuracy and if there are glaring omissions. Please provide any feedback prior to 2022-06-22 0:00 AoE. Thanks, Jonathan The PostgreSQL Global Development Group announces that t

Re: PostgreSQL 15 beta 2 release announcement draft

On 6/29/22 2:55 AM, Pantelis Theodosiou wrote: Upgrading to PostgreSQL 15 Beta 2 - To upgrade to PostgreSQL 15 Beta 2 from an earlier version of PostgreSQL, you will need to use a strategy similar to upgrading between major versions of PostgreSQL (e.g. `pg_upgrade

Re: PostgreSQL 15 beta 2 release announcement draft

On 6/29/22 2:12 AM, Erik Rijkers wrote: Op 29-06-2022 om 02:04 schreef Jonathan S. Katz: Hi, 'not advise you to run PostgreSQL 15 Beta 1'    should be 'not advise you to run PostgreSQL 15 Beta 2' Thanks; I adjusted the copy. Jonathan OpenPGP_signature Descript

Re: PostgreSQL 15 beta 2 release announcement draft

On 6/29/22 9:30 AM, Tom Lane wrote: "Jonathan S. Katz" writes: On 6/29/22 2:55 AM, Pantelis Theodosiou wrote: Is the major version upgrade still needed if they are upgrading from 15 Beta 1? No, but it would be required if you a upgrading from a different version. The language a

Re: PostgreSQL 15 beta 2 release announcement draft

On 6/29/22 3:07 PM, Erik Rijkers wrote: Op 29-06-2022 om 02:04 schreef Jonathan S. Katz: Hi, Attached is a draft of the release announcement for PostgreSQL 15 Beta 2. Please provide feedback on technical accuracy and if there are glaring omissions. Hardly 'glaring' but still:

Re: PG15 beta1 sort performance regression due to Generation context change

Hi David, On 7/13/22 12:13 AM, David Rowley wrote: On Tue, 12 Jul 2022 at 17:15, David Rowley wrote: So far only Robert has raised concerns with this regression for PG15 (see [2]). Tom voted for leaving things as they are for PG15 in [3]. John agrees, as quoted above. Does anyone else have any

Re: PG15 beta1 sort performance regression due to Generation context change

On 7/15/22 4:36 PM, Tomas Vondra wrote: On 7/13/22 17:32, Andres Freund wrote: Hi, On 2022-07-13 09:23:00 -0400, Jonathan S. Katz wrote: On 7/13/22 12:13 AM, David Rowley wrote: On Tue, 12 Jul 2022 at 17:15, David Rowley wrote: So far only Robert has raised concerns with this regression

Re: PG15 beta1 sort performance regression due to Generation context change

On 7/15/22 4:54 PM, Tom Lane wrote: Tomas Vondra writes: ... My personal opinion is that it's a rare regression. Other optimization patches have similar rare regressions, except that David spent so much time investigating this one it seems more serious. Yeah, this. I fear we're making a moun

Re: PG15 beta1 sort performance regression due to Generation context change

On 7/15/22 6:40 PM, Jonathan S. Katz wrote: On 7/15/22 4:54 PM, Tom Lane wrote: Tomas Vondra writes: ... My personal opinion is that it's a rare regression. Other optimization patches have similar rare regressions, except that David spent so much time investigating this one it seems

Re: PG15 beta1 sort performance regression due to Generation context change

Thank you for the very detailed analysis. Comments inline. On 7/15/22 7:12 PM, David Rowley wrote: On Sat, 16 Jul 2022 at 10:40, Jonathan S. Katz wrote: What I find interesting is the resistance to adding any documentation around this feature to guide users in case they hit the regression. I

Re: PG15 beta1 sort performance regression due to Generation context change

On 7/15/22 6:52 PM, Andres Freund wrote: Hi, On 2022-07-15 18:40:11 -0400, Jonathan S. Katz wrote: What I find interesting is the resistance to adding any documentation around this feature to guide users in case they hit the regression. I understand it can be difficult to provide guidance on

Re: Handle infinite recursion in logical replication setup

Hi, On 7/21/22 6:34 AM, vignesh C wrote: On Thu, Jul 21, 2022 at 2:06 PM Amit Kapila wrote: On Wed, Jul 20, 2022 at 2:33 PM vignesh C wrote: Modified. Apart from this I have run pgperltidy on the perl file and renamed 032_origin.pl to 030_origin.pl as currently there is 029_on_error.pl, 03

Re: Handle infinite recursion in logical replication setup

On 7/22/22 12:47 AM, Amit Kapila wrote: On Fri, Jul 22, 2022 at 1:39 AM Jonathan S. Katz wrote: 1. I'm concerned by calling this "Bidirectional replication" in the docs that we are overstating the current capabilities. I think this is accentuated int he opening par

Re: Handle infinite recursion in logical replication setup

On 7/25/22 4:54 AM, vignesh C wrote: On Sun, Jul 24, 2022 at 10:21 PM Jonathan S. Katz wrote: On 7/22/22 12:47 AM, Amit Kapila wrote: On Fri, Jul 22, 2022 at 1:39 AM Jonathan S. Katz wrote: BTW, do you have any opinion on the idea of the first remaining patch where we accomplish two

Re: pg15b2: large objects lost on upgrade

On 7/30/22 10:40 AM, Tom Lane wrote: Noah Misch writes: The pg_backend_pid is from "SELECT pg_catalog.pg_backend_pid();" in ~/.psqlrc, so the lack of -X caused that. The latest commit fixes things on a normal GNU/Linux box, so I bet it will fix wrasse. Yup, looks like we're all good now. Th

Re: pg15b2: large objects lost on upgrade

On 8/2/22 1:12 PM, Tom Lane wrote: "Jonathan S. Katz" writes: Given this appears to be resolved, I have removed this from "Open Items". Thanks! Sadly, we're still not out of the woods. I see three buildfarm failures in this test since Robert resolved the "-X

Re: pg15b2: large objects lost on upgrade

On 8/2/22 3:23 PM, Robert Haas wrote: On Tue, Aug 2, 2022 at 1:12 PM Tom Lane wrote: Not sure what to make of this, except that maybe the test is telling us about an actual bug of exactly the kind it's designed to expose. That could be, but what would the bug be exactly? It's hard to think of

Re: pg15b2: large objects lost on upgrade

On 8/2/22 3:39 PM, Tom Lane wrote: "Jonathan S. Katz" writes: On 8/2/22 3:23 PM, Robert Haas wrote: I'm not quite sure how to rule that theory in or out, though. Without overcomplicating this, are we able to check to see if autovacuum ran during the course of the test? L

Re: pg15b2: large objects lost on upgrade

On 8/2/22 3:51 PM, Tom Lane wrote: "Jonathan S. Katz" writes: On 8/2/22 3:39 PM, Tom Lane wrote: I am not in favor of disabling autovacuum in the test: ordinary users are not going to do that while pg_upgrade'ing, so it'd make the test less representative of real-world usa

Re: pg15b2: large objects lost on upgrade

On 8/2/22 4:20 PM, Jonathan S. Katz wrote: On 8/2/22 3:51 PM, Tom Lane wrote: "Jonathan S. Katz" writes: On 8/2/22 3:39 PM, Tom Lane wrote: I am not in favor of disabling autovacuum in the test: ordinary users are not going to do that while pg_upgrade'ing, so it'

Re: pg15b2: large objects lost on upgrade

> On Aug 3, 2022, at 10:14 AM, Tom Lane wrote: > > Robert Haas writes: >>> On Tue, Aug 2, 2022 at 3:51 PM Tom Lane wrote: >>> I also think that ">=" is a sufficient requirement. > >> I don't really like this approach. Imagine that the code got broken in >> such a way that relfrozenxid and r

Re: pg15b2: large objects lost on upgrade

On 8/3/22 2:08 PM, Peter Geoghegan wrote: On Wed, Aug 3, 2022 at 1:47 PM Tom Lane wrote: Again, this seems to me to be breaking the test's real-world applicability for a (false?) sense of stability. I agree. A lot of the VACUUM test flappiness issues we've had to deal with in the past now se

Re: pg15b2: large objects lost on upgrade

On 8/3/22 4:19 PM, Tom Lane wrote: "Jonathan S. Katz" writes: I did rule out wanting to do the "xid + $X" check after reviewing some of the output. I think that both $X could end up varying, and it really feels like a bandaid. It is that. I wouldn't feel comfortable

2022-08-11 release announcement draft

Hi, Please see attached draft of the 2022-08-11 release announcement. Please provide feedback on {technical accuracy, omissions, any other errors} no later than 2022-08-11 0:00 AoE[1]. Thanks, Jonathan [1] https://en.wikipedia.org/wiki/Anywhere_on_Earth The PostgreSQL Global Development Gro

Re: 2022-08-11 release announcement draft

On 8/8/22 12:44 PM, Justin Pryzby wrote: On Mon, Aug 08, 2022 at 11:50:16AM -0400, Jonathan S. Katz wrote: * Fix [`pg_upgrade`](https://www.postgresql.org/docs/current/pgupgrade.html) to detect non-upgradable usages of functions accepting `anyarray` parameters. use or usage This line comes

Re: PG 15 (and to a smaller degree 14) regression due to ExprEvalStep size

On 8/5/22 4:36 PM, Andres Freund wrote: Hi, I tried to look into some of the questions from Amit, but I have e.g. no idea what exactly the use of subtransactions tries to achieve - afaics 1a36bc9dba8 is the first patch to introduce needing to evaluate parts expressions in a subtransaction - but

Re: PG 15 (and to a smaller degree 14) regression due to ExprEvalStep size

On 8/9/22 11:03 AM, Andrew Dunstan wrote: On 2022-08-09 Tu 09:59, Jonathan S. Katz wrote: The RMT met today to discuss the state of this open item surrounding the SQL/JSON feature set. We discussed the specific concerns raised about the code and debated four different options:   1. Do

Re: PG 15 (and to a smaller degree 14) regression due to ExprEvalStep size

On 8/9/22 3:22 PM, Andres Freund wrote: Hi, On 2022-08-09 15:17:44 -0400, Tom Lane wrote: We have delayed releases for $COOL_FEATURE in the past, and I think our batting average on that is still .000: not once has it worked out well. I think it semi worked when jsonb (?) first went in - it to

Re: PG 15 (and to a smaller degree 14) regression due to ExprEvalStep size

On 8/9/22 2:57 PM, Andres Freund wrote: Hi, On 2022-08-09 14:04:48 -0400, Jonathan S. Katz wrote:   2. Recommend holding up the v15 release to allow for the code to be redesigned and fixed (as based on Andres' estimates, this would push the release out several months). Obviously tha

Re: PG 15 (and to a smaller degree 14) regression due to ExprEvalStep size

On 8/9/22 4:15 PM, Andrew Dunstan wrote: On 2022-08-09 Tu 15:50, Jonathan S. Katz wrote: On 8/9/22 3:22 PM, Andres Freund wrote: OTOH, it's not a great sign  this is around json again... Yeah, I was thinking about that too. Ouch :-( I think after 10 years of being involved wit

SQL/JSON features for v15

Hi, (Personal hat, not RMT hat unless otherwise noted). This thread[1] raised some concerns around the implementation of the SQL/JSON features that are slated for v15, which includes an outstanding open item[2]. Given the current state of the discussion, when the RMT met on Aug 8, they severa

Re: SQL/JSON features for v15

On 8/9/22 4:58 PM, Jonathan S. Katz wrote: We're looking for additional input on what makes sense as a best course of action, given what is presented in[3]. Missed adding Amit on the CC. Jonathan OpenPGP_signature Description: OpenPGP digital signature

Re: moving basebackup code to its own directory

On 8/10/22 12:32 PM, Magnus Hagander wrote: On Wed, Aug 10, 2022 at 6:20 PM Tom Lane wrote: Robert Haas writes: David Steele voted for back-patching this on the grounds that it would make future back-patching easier, which is an argument that seems to me to have some merit, although on the o

Re: SQL/JSON features for v15

On 8/10/22 11:50 AM, Andrew Dunstan wrote: On 2022-08-09 Tu 16:58, Jonathan S. Katz wrote: Hi, (Personal hat, not RMT hat unless otherwise noted). This thread[1] raised some concerns around the implementation of the SQL/JSON features that are slated for v15, which includes an outstanding

Re: PG 15 (and to a smaller degree 14) regression due to ExprEvalStep size

On 8/10/22 9:27 AM, Amit Langote wrote: On Wed, Aug 10, 2022 at 3:57 AM Andres Freund wrote: One way this code could be drastically simplified is to force all type-coercions to go through the "io coercion" path, which could be implemented as a single execution step (which thus could trivially s

Re: Release 14 Schedule

On 9/19/21 12:32 PM, Justin Pryzby wrote: > On Sat, Sep 18, 2021 at 01:37:19PM -0400, Tom Lane wrote: >> We don't yet have a list-of-major-features for the v14 release notes. >> Anybody care to propose one? > > . Allow extended statistics on column expressions; > . Memoize node which can impro

PostgreSQL 14 press release draft

Hi, Attached is a copy of the first draft for the PG14 press release. This brings together highlights of many of the features in the upcoming PostgreSQL 14 release while providing context on their significance. With the plethora of new features coming in PostgreSQL 14, it is challenging to highli

Re: Release 14 Schedule

On 9/20/21 2:33 AM, Nikolay Samokhvalov wrote: > Observability-related improvements are also good and very important for > the future of DBA operations -- compute_query_id, new pg_stat_**, etc. > > Things like new knob idle_session_timeout and restore_command change not > requiring a restart will

Re: PostgreSQL 14 press release draft

On 9/21/21 12:09 AM, Justin Pryzby wrote: > On Mon, Sep 20, 2021 at 10:19:32PM -0400, Jonathan S. Katz wrote: > >> PostgreSQL 14 provides a significant throughput boost on workloads that use >> many >> connections, with some benchmarks showing a 2x speedup. This release

Re: PostgreSQL 14 press release draft

On 9/22/21 10:17 AM, Jonathan S. Katz wrote: > Updated draft attached. As a reminder, please provide any feedback on > the press release no later than **Thu, Sep 23, 2021 @ 18:00 UTC**. I'm sure it helps if I actually attach the draft. Jonathan The PostgreSQL Global Development

Re: Release 14 Schedule

On 9/22/21 11:15 AM, Magnus Hagander wrote: > On Wed, Sep 22, 2021 at 5:12 PM Tom Lane wrote: >> >> "Jonathan S. Katz" writes: >>> On 9/19/21 12:32 PM, Justin Pryzby wrote: >>>> On Sat, Sep 18, 2021 at 01:37:19PM -0400, Tom Lane wrote: >>>&g

Re: Release 14 Schedule

On 9/22/21 12:30 PM, Tom Lane wrote: > "Jonathan S. Katz" writes: >> On 9/22/21 11:15 AM, Magnus Hagander wrote: >>> I have a feeling emergency mode vacuum fits on that list. Not in the >>> press release, but in the major features list of the release note

Re: Release 14 Schedule

On 9/22/21 10:43 PM, Peter Geoghegan wrote: > On Wed, Sep 22, 2021 at 7:06 PM Tom Lane wrote: >> Ummm ... RC1 was wrapped on Monday. It will go out with the "TO BE ADDED" >> placeholder for this list. I'm not panicked about time --- we just need >> to finalize this text by Sunday-ish. > > I ass

Re: PostgreSQL 14 press release draft

On 9/22/21 12:57 PM, Greg Sabino Mullane wrote: > Some super quick nitpicks; feel free to ignore/apply/laugh off. Thanks. I incorporated many of the suggestions. Here is the press release at is stands. As we are past the deadline for feedback, we are going to start the translation effort for the

Re: unnesting multirange data types

On 7/15/21 12:26 PM, Alexander Korotkov wrote: > On Thu, Jul 15, 2021 at 6:47 PM Tom Lane wrote: >> Yeah, that seems pretty horrid. I still don't like the way the >> array casts were done, but I'd be okay with pushing the unnest >> addition. > > +1 for just unnest(). ...which was my original as

2021-08-12 release announcement draft

Hi, Attached is a draft for the 2021-08-12 release announcement. Please review for technical accuracy. Please ensure you have your feedback in no later than midnight today (Aug 11) AoE[1]. Thanks! Jonathan [1] https://en.wikipedia.org/wiki/Anywhere_on_Earth The PostgreSQL Global Development Gr

Re: 2021-08-12 release announcement draft

On 8/11/21 1:35 PM, Peter Geoghegan wrote: > On Wed, Aug 11, 2021 at 9:32 AM Jonathan S. Katz wrote: >> Please ensure you have your feedback in no later than midnight today >> (Aug 11) AoE[1]. > > I think that the pg_upgrade item should say that we now avoid forcing > a

Re: 2021-08-12 release announcement draft

On 8/11/21 2:29 PM, Peter Geoghegan wrote: > On Wed, Aug 11, 2021 at 11:23 AM Jonathan S. Katz > wrote: >> How about: >> >> * `pg_upgrade` now carries forward the old installation's `oldestXID` >> value, which can improve things from a performance standpo

Re: 2021-08-12 release announcement draft

On 8/11/21 2:46 PM, Justin Pryzby wrote: > On Wed, Aug 11, 2021 at 12:32:41PM -0400, Jonathan S. Katz wrote: > >> * walsenders now show their latest replication commands in >> `pg_stat_activity`, >> instead of just showing the latest SQL command. > > singular

Re: 2021-08-12 release announcement draft

On 8/11/21 7:25 PM, David Rowley wrote: > Thanks for drafting this up. > > On Thu, 12 Aug 2021 at 04:32, Jonathan S. Katz wrote: >> Please ensure you have your feedback in no later than midnight today >> (Aug 11) AoE[1]. > > It might not be the exact technical feed

Re: 2021-08-12 release announcement draft

On 8/11/21 8:53 PM, Jonathan S. Katz wrote: > On 8/11/21 7:25 PM, David Rowley wrote: > I've updated it to: > > "This release marks the third beta release of PostgreSQL 14 and puts the > community one step closer to general availability around the end of the > third

Re: Trying out read streams in pgvector (an extension)

On 6/11/24 12:53 AM, Thomas Munro wrote: Hi, I was looking around for an exotic index type to try the experience of streamifying an extension, ie out-of-core code. I am totally new to pgvector, but since everyone keeps talking about it, I could not avoid picking up some basic facts in the pgcon

Re: Conflict Detection and Resolution

On 6/13/24 7:28 AM, Amit Kapila wrote: You are right that users would wish to detect the conflicts and probably the extra effort would only be in the 'update_differ' case where we need to consult committs module and that we will only do when 'track_commit_timestamp' is true. BTW, I think for Ins

PostgreSQL 17 Beta 2 release date & commit freeze

Hi, PostgreSQL 17 Beta 2 is planned to be release on June 27, 2024. Please continue your hard work on closing out open items[1] ahead of the release and have the fixes targeted for the release committed by June 22, 2024. Thanks! Jonathan [1] https://wiki.postgresql.org/wiki/PostgreSQL_17_

Re: Incremental sort for access method with ordered scan support (amcanorderbyop)

On 7/5/23 2:15 AM, Richard Guo wrote: On Tue, Jul 4, 2023 at 7:15 PM David Rowley > wrote: On Tue, 4 Jul 2023 at 20:12, Richard Guo mailto:guofengli...@gmail.com>> wrote: > The v4 patch looks good to me (maybe some cosmetic tweaks are still > needed f

Re: psql: Add role's membership options to the \du+ command

On 7/19/23 1:44 PM, Pavel Luzanov wrote: On 19.07.2023 19:47, Tom Lane wrote: And done, with some minor editorialization. Thanks to everyone who participated in the work. Special thanks to David for moving forward this patch for a long time, and to Tom for taking commit responsibilities. [R

PostgreSQL 16 Beta 3 release date

Hi, The release date for PostgreSQL 16 Beta 3 is August 10, 2023, alongside the regular update release[1]. Please be sure to commit any open items[2] for the Beta 3 release before August 6, 2023 0:00 AoE[3] to give them enough time to work through the buildfarm. Thanks, Jonathan [1] https

Re: [PoC] pg_upgrade: allow to upgrade publisher node

On 8/1/23 5:39 AM, Amit Kapila wrote: On Fri, Jul 28, 2023 at 5:48 PM vignesh C wrote: Here is a patch which checks that there are no WAL records other than CHECKPOINT_SHUTDOWN WAL record to be consumed based on the discussion from [1]. Few comments: = 2. + if (dopt.logical_s

2023-08-10 release announcement draft

Hi, Attached is the release announcement draft for the 2023-08-10 update release, which also includes the release of PostgreSQL 16 Beta 3. Please provide your feedback no later than August 10, 2023 0:00 AoE[1]. Thanks, Jonathan [1] https://en.wikipedia.org/wiki/Anywhere_on_Earth The Postgre

Re: 2023-08-10 release announcement draft

On 8/7/23 9:45 PM, David Rowley wrote: * Fix a performance regression when running concurrent [`COPY`](https://www.postgresql.org/docs/16/sql-copy.html) statements on a single table. I think this is still outstanding. A bit of work has been done for the int parsing regression but it seems ther

Re: 2023-08-10 release announcement draft

On 8/7/23 9:53 PM, David Rowley wrote: On Tue, 8 Aug 2023 at 13:49, Jonathan S. Katz wrote: On 8/7/23 9:45 PM, David Rowley wrote: * Fix a performance regression when running concurrent [`COPY`](https://www.postgresql.org/docs/16/sql-copy.html) statements on a single table. I think this

Re: 2023-08-10 release announcement draft

On 8/8/23 1:30 AM, Erik Rijkers wrote: Op 8/8/23 om 03:15 schreef Jonathan S. Katz: Please provide your feedback no later than August 10, 2023 0:00 AoE[1]. 'You us'  should be 'You use'    (2x) It should actually be just "Use" -- but I've fixe

Re: 2023-08-10 release announcement draft

On 8/9/23 1:04 AM, Noah Misch wrote: On Mon, Aug 07, 2023 at 10:03:44PM -0400, Jonathan S. Katz wrote: Fixes in PostgreSQL 16 Beta 3 - The following includes fixes included in PostgreSQL 16 Beta 3: With both "includes" and "included" th

Re: 2023-08-10 release announcement draft

On 8/8/23 11:13 PM, Robert Treat wrote: "Users who have skipped one or more update releases may need to run additional, post-update steps; " The comma should be removed. "please see the release notes for earlier versions for details." Use of 'for' twice is grammatically incorrect; I am partia

PostgreSQL 16 RC1 + GA release dates

Hi, The date for PostgreSQL 16 Release Candidate 1 (RC1) is August 31, 2023. Please ensure all open items[1] are completed and committed before August 26, 2023 12:00 UTC. This means the current target date for the PostgreSQL 16 GA release is September 14, 2023. While this date could change i

PostgreSQL 16 release announcement draft

Hi, Attached is the first draft of the PostgreSQL 16 release announcement, authored by Chelsea Dole & myself. To frame this up, the goal of the GA release announcement is to help folks discover the awesome new features of PostgreSQL. It's impossible to list out every single feature in the re

Re: PostgreSQL 16 RC1 + GA release dates

On 8/20/23 10:50 AM, Tom Lane wrote: "Jonathan S. Katz" writes: The date for PostgreSQL 16 Release Candidate 1 (RC1) is August 31, 2023. Please ensure all open items[1] are completed and committed before August 26, 2023 12:00 UTC. FYI, I moved the "Oversight in reparameteriz

Re: PostgreSQL 16 release announcement draft

On 8/23/23 8:02 AM, David Rowley wrote: On Wed, 23 Aug 2023 at 22:21, jian he wrote: PostgreSQL 16 improves the performance of existing PostgreSQL functionality through new query planner optimizations. In this latest release, the query planner can parallelize `FULL` and `RIGHT` joins, util

Re: PostgreSQL 16 release announcement draft

On 8/23/23 5:07 PM, David Rowley wrote: On Thu, 24 Aug 2023 at 05:55, Jonathan S. Katz wrote: We could add something about 1349d2790 -- do you have suggested wording? I think it's worth a mention. See the text added in square brackets below: PostgreSQL 16 improves the performan

Re: PostgreSQL 16 release announcement draft

On 8/24/23 11:16 AM, jian he wrote: hi. Can you check my first email about "a" versus "the" and "pg_stat_activity". I did when you first sent it, and did not make any changes. also: "including the `\bind` command, which allows users to execute parameterized queries (e.g `SELECT $1 + $2`) then

Re: PostgreSQL 16 RC1 + GA release dates

On 8/16/23 3:48 PM, Jonathan S. Katz wrote: The date for PostgreSQL 16 Release Candidate 1 (RC1) is August 31, 2023. Please ensure all open items[1] are completed and committed before August 26, 2023 12:00 UTC. Reminder: the RC1 open item[1] deadline is at August 26, 2023 @ 12:00 UTC

Re: PostgreSQL 16 release announcement draft

On 8/24/23 12:54 PM, Dave Cramer wrote: > Postgres, PostgreSQL, and the Elephant Logo (Slonik) are all registered > trademarks of the [PostgreSQL Community Association of Canada](https://www.postgres.ca ). Isn't this just the "PostgreSQL Communit

Re: PostgreSQL 16 release announcement draft

On 8/24/23 11:17 AM, Erik Rijkers wrote: Op 8/24/23 om 16:32 schreef Jonathan S. Katz: On 8/23/23 5:07 PM, David Rowley wrote: On Thu, 24 Aug 2023 at 05:55, Jonathan S. Katz wrote: Hi, When v15 docs have: "27.2.7. Cascading Replication The cascading replication feature allows a st

Re: PostgreSQL 16 release announcement draft

On 8/24/23 11:19 AM, Alvaro Herrera wrote: On 2023-Aug-24, Jonathan S. Katz wrote: ### Performance Improvements PostgreSQL 16 improves the performance of existing PostgreSQL functionality through new query planner optimizations. In this latest release, the query planner can parallelize `FULL

PostgreSQL 16 RC1 release announcement draft

Hi, Attached is the PostgreSQL 16 RC1 release announcement draft. Currently there is only one item in it, as there was only one open item marked as closed. If there are any other fixes for the RC1 that were specific to v16 and should be included in the announcement, please let me know. Plea

Re: Reports on obsolete Postgres versions

On 4/12/24 2:12 PM, Bruce Momjian wrote: I am ready to apply this patch to the website. How do I do this? Do I just commit this to the pgweb git tree? Does that push to the website? I pushed this to the website[1]. Thanks, Jonathan [1] https://www.postgresql.org/support/versioning/ Op

PostgreSQL 17 Beta 1 release date

Hi, PostgreSQL 17 Beta 1 is planned to be release on May 23, 2024. Please continue your hard work on closing out open items[1] ahead of the release and have the fixes targeted for the release committed by May 18, 2024. Thanks - it's very exciting that we're at this point in the release cycle

New committers: Melanie Plageman, Richard Guo

The Core Team would like to extend our congratulations to Melanie Plageman and Richard Guo, who have accepted invitations to become our newest PostgreSQL committers. Please join us in wishing them much success and few reverts! Thanks, Jonathan OpenPGP_signature.asc Description: OpenPGP digi

2024-05-09 release announcement draft

Hi, Please find the draft of the 2024-05-09 release announcement. Please review for corrections and any omissions that should be called out as part of this release. Please provide feedback no later (and preferably sooner) than 2024-05-09 12:00 UTC. Thanks, Jonathan The PostgreSQL Global D

Re: 2024-05-09 release announcement draft

On 5/6/24 5:08 PM, David Rowley wrote: On Tue, 7 May 2024 at 05:44, Jonathan S. Katz wrote: Please provide feedback no later (and preferably sooner) than 2024-05-09 12:00 UTC. Thanks for the draft. Here's some feedback. * Fix [`INSERT`](https://www.postgresql.org/docs/curren

Re: 2024-05-09 release announcement draft,2024-05-09 release announcement draft

On 5/6/24 5:36 PM, Sutou Kouhei wrote: Hi, In <779790c7-45d7-4010-9305-c3f9e6a60...@postgresql.org>,<779790c7-45d7-4010-9305-c3f9e6a60...@postgresql.org> "2024-05-09 release announcement draft,2024-05-09 release announcement draft" on Mon, 6 May 2024 13:44:05 -0400

Re: 2024-05-09 release announcement draft

On 5/6/24 11:05 PM, David Rowley wrote: On Tue, 7 May 2024 at 14:58, Jonathan S. Katz wrote: * Throw an error if an index is accessed while it is being reindexed. Based on this, I'd vote to just remove it from the release announcement. I'd prefer that over leaving the wording

Re: 2024-05-09 release announcement draft

On 5/7/24 12:16 AM, Tom Lane wrote: David Rowley writes: Why not "Fix INSERT with multi-row VALUES clauses ..."? To my mind, the VALUES clause is the data source for INSERT, so "from" seems appropriate. I'm not going to argue hard about it. OK, so I've read through this a few times and hav

Re: 2024-05-09 release announcement draft

On 5/8/24 5:44 PM, David Rowley wrote: On Thu, 9 May 2024 at 04:17, Jonathan S. Katz wrote: * Fix how [`INSERT`](https://www.postgresql.org/docs/current/sql-insert.html) handles multiple [`VALUES`](https://www.postgresql.org/docs/current/sql-values.html) rows into a target column that is a

PostgreSQL 17 Beta 1 release announcement draft

Hi, Attached is a copy of the PostgreSQL 17 Beta 1 release announcement draft. This contains a user-facing summary of some of the features that will be available in the Beta, as well as a call to test. I've made an effort to group them logically around the different workflows they affect. A

Re: PostgreSQL 17 Beta 1 release announcement draft

On 5/15/24 10:42 PM, David Rowley wrote: Thanks for writing that up. It's always exciting to see this each year. On Thu, 16 May 2024 at 13:45, Jonathan S. Katz wrote: * Please indicate if you believe there's a notable omission, or if we should omit any of these callouts I

Re: PostgreSQL 17 Beta 1 release announcement draft

On 5/16/24 1:10 AM, Thom Brown wrote: On Thu, May 16, 2024, 02:45 Jonathan S. Katz <mailto:jk...@postgresql.org>> wrote: Hi, Attached is a copy of the PostgreSQL 17 Beta 1 release announcement draft. This contains a user-facing summary of some of the features that

Re: PostgreSQL 17 Beta 1 release announcement draft

On 5/16/24 1:15 AM, Bertrand Drouvot wrote: Hi, On Wed, May 15, 2024 at 09:45:35PM -0400, Jonathan S. Katz wrote: Hi, Attached is a copy of the PostgreSQL 17 Beta 1 release announcement draft. Thanks for working on it! I've one comment: PostgreSQL 17 also introduces a new

Re: PostgreSQL 17 Beta 1 release announcement draft

On 5/16/24 6:41 AM, Jelte Fennema-Nio wrote: On Thu, 16 May 2024 at 03:45, Jonathan S. Katz wrote: Attached is a copy of the PostgreSQL 17 Beta 1 release announcement draft. I think we can quickly mention c4ab7da6061 in the COPY paragraph, in some benchmarks it improved perf by close to 2x

Re: PostgreSQL 17 Beta 1 release announcement draft

On 5/16/24 8:05 AM, Joe Conway wrote: On 5/15/24 21:45, Jonathan S. Katz wrote: Please provide feedback no later than Wed 2024-05-22 18:00 UTC. As the beta release takes some extra effort, I want to ensure all changes are in with time to spare before release day. "You can find inform

Re: PostgreSQL 17 Beta 1 release announcement draft

On 5/15/24 9:45 PM, Jonathan S. Katz wrote: Hi, Attached is a copy of the PostgreSQL 17 Beta 1 release announcement draft. This contains a user-facing summary of some of the features that will be available in the Beta, as well as a call to test. I've made an effort to group them logi

Re: PostgreSQL 17 Beta 1 release announcement draft

On 5/19/24 7:24 PM, David Rowley wrote: On Mon, 20 May 2024 at 09:35, Jonathan S. Katz wrote: Thanks for all the feedback to date. Please see the next revision. Again, please provide feedback no later than 2024-05-22 18:00 UTC. Thanks for the updates. [`COPY`](https://www.postgresql.org

Re: PostgreSQL 17 Beta 1 release announcement draft

On 5/20/24 2:58 AM, John Naylor wrote: Hi Jon, Regarding vacuum "has shown up to a 6x improvement in overall time to complete its work" -- I believe I've seen reported numbers close to that only 1) when measuring the index phase in isolation or maybe 2) the entire vacuum of unlogged tables with

Re: PostgreSQL 17 Beta 1 release announcement draft

On 5/20/24 8:31 AM, jian he wrote: release note (https://momjian.us/pgsql_docs/release-17.html) is "Add jsonpath methods to convert JSON values to other JSON data types (Jeevan Chalke)" Additionally, PostgreSQL 17 adds more functionality to its `jsonpath` implementation, including the abilit

Re: PostgreSQL 17 Beta 1 release announcement draft

On 5/20/24 6:32 AM, David Rowley wrote: On Mon, 20 May 2024 at 22:11, Alvaro Herrera wrote: On 2024-May-16, David Rowley wrote: On Thu, 16 May 2024 at 17:37, zaidagilist wrote: I am trying to open the 17 docs but it looks removed. Getting following message "Page not found" https://www.pos

Re: PostgreSQL 17 Beta 1 release announcement draft

On 5/20/24 5:34 AM, Bertrand Drouvot wrote: Hi, On Sun, May 19, 2024 at 05:10:10PM -0400, Jonathan S. Katz wrote: On 5/16/24 1:15 AM, Bertrand Drouvot wrote: Hi, On Wed, May 15, 2024 at 09:45:35PM -0400, Jonathan S. Katz wrote: Hi, Attached is a copy of the PostgreSQL 17 Beta 1 release

Re: PostgreSQL 17 Beta 1 release announcement draft

On 5/19/24 6:15 PM, Erik Rijkers wrote: Op 5/19/24 om 23:34 schreef Jonathan S. Katz: On 5/15/24 9:45 PM, Jonathan S. Katz wrote: Hi, Attached is a copy of the PostgreSQL 17 Beta 1 release announcement 'This release introduces adds an interface'  should be: 'This release ad

Re: PostgreSQL 17 Beta 1 release announcement draft

On 5/20/24 6:08 AM, Alvaro Herrera wrote: On 2024-May-19, Jonathan S. Katz wrote: ### Query and Operational Performance Improvements In this section I'd add mention the new GUCs to control SLRU memory size, which is going to be a huge performance boon for cases where the current fixed

Re: PostgreSQL 17 Beta 1 release announcement draft

On 5/21/24 6:40 AM, John Naylor wrote: On Mon, May 20, 2024 at 8:41 PM Masahiko Sawada wrote: On Mon, May 20, 2024 at 8:47 PM Jonathan S. Katz wrote: On 5/20/24 2:58 AM, John Naylor wrote: Hi Jon, Regarding vacuum "has shown up to a 6x improvement in overall time to complete its

<    1   2   3   4   5   6   7   >