New committer: Jacob Champion

The Core Team would like to extend our congratulations to Jacob Champion, who has accepted an invitation to become our newest PostgreSQL committer. Please join us in wishing Jacob much success and few reverts! Thanks, Jonathan OpenPGP_signature.asc Description: OpenPGP digital signature

Out-of-cycle release on 2025-02-20

Hi, CVE-2025-1094[1] introduced a regression that was reported fairly shortly after the release[2]. Based on the nature of the report and the fact it's in libpq, the release team was unsure of what the overall prevalence of the issue given its client-facing, and decided to have an out-of-cycl

2025-02-13 release announcement draft

Hi, Attached is a draft of the 2025-02-13 update release announcement. Please provide feedback no later than 2025-02-13 0:00 UTC. Thanks, Jonathan The PostgreSQL Global Development Group has released an update to all supported versions of PostgreSQL, including 17.3, 16.7, 15.11, 14.16, and 13

Re: Add support to TLS 1.3 cipher suites and curves lists

On 12/11/24 10:14 AM, Daniel Gustafsson wrote: On 11 Dec 2024, at 18:47, Tom Lane wrote: Oh yay, another naming problem :-(. I think that neither "ciphers" vs. "cipher suites" nor "ssl_ciphers" vs. "ssl_ciphers_tlsv13" is going to convey a lot to the average person who's not steeped in TLS m

Re: IMPORTANT: Out-of-cycle release scheduled for November 21, 2024

On 11/20/24 10:08 PM, Bruce Momjian wrote: On Wed, Nov 20, 2024 at 09:51:09PM -0500, Jonathan Katz wrote: On 11/20/24 9:50 PM, Jonathan S. Katz wrote: On 11/20/24 9:48 PM, Tom Lane wrote: "David G. Johnston" writes: On Wed, Nov 20, 2024 at 7:18 PM Bruce Momjian wrote: so when

Re: IMPORTANT: Out-of-cycle release scheduled for November 21, 2024

On 11/20/24 9:48 PM, Tom Lane wrote: "David G. Johnston" writes: On Wed, Nov 20, 2024 at 7:18 PM Bruce Momjian wrote: so when we decided to remove the downloads Can you elaborate on who "we" is here? More to the point, what downloads were removed? I still see the source tarballs in the

Re: IMPORTANT: Out-of-cycle release scheduled for November 21, 2024

On 11/20/24 9:50 PM, Jonathan S. Katz wrote: On 11/20/24 9:48 PM, Tom Lane wrote: "David G. Johnston" writes: On Wed, Nov 20, 2024 at 7:18 PM Bruce Momjian wrote: so when we decided to remove the downloads Can you elaborate on who "we" is here? More to the point,

Re: IMPORTANT: Out-of-cycle release scheduled for November 21, 2024

On 11/20/24 9:18 PM, Bruce Momjian wrote: On Fri, Nov 15, 2024 at 06:28:42PM -0500, Jonathan Katz wrote: We're scheduling an out-of-cycle release on November 21, 2024 to address two regressions that were released as part of the November 14, 2024 update release[1]. As part of this release, we wil

IMPORTANT: Out-of-cycle release scheduled for November 21, 2024

We're scheduling an out-of-cycle release on November 21, 2024 to address two regressions that were released as part of the November 14, 2024 update release[1]. As part of this release, we will issue fixes for all supported versions (17.2, 16.6, 15.10, 14.15, 13.20), and for 12.22, even though P

Re: 2024-11-14 release announcement draft

On 11/14/24 2:55 AM, jian he wrote: On Tue, Nov 12, 2024 at 12:28 PM Jonathan S. Katz wrote: Hi, Please review the draft of the release announcement for the 2024-11-14 release. Please provide any feedback by 2024-11-14 12:00 UTC. someone reminded me. i am wondering do we need include the

Re: 2024-11-14 release announcement draft

On 11/11/24 11:54 PM, Thomas Munro wrote: On Tue, Nov 12, 2024 at 5:28 PM Jonathan S. Katz wrote: Please review the draft of the release announcement for the 2024-11-14 release. Please provide any feedback by 2024-11-14 12:00 UTC. I think "* Fixes random crashes in JIT compilation on aa

2024-11-14 release announcement draft

Hi, Please review the draft of the release announcement for the 2024-11-14 release. Please provide any feedback by 2024-11-14 12:00 UTC. Thanks! Jonathan The PostgreSQL Global Development Group has released an update to all supported versions of PostgreSQL, including 17.1, 16.5, 15.9, 14.14,

Re: sunsetting md5 password support

On 10/9/24 3:55 PM, Nathan Bossart wrote: In this message, I propose a multi-year, incremental approach to remove MD5 password support from Postgres. +100; thanks for a concrete proposal. Cutting out the "well-understood" problems bit.> Given there is a battle-tested alternative to MD5, I pro

Re: Should rolpassword be toastable?

On 10/3/24 7:29 PM, Jacob Champion wrote: On Thu, Oct 3, 2024 at 3:25 PM Tom Lane wrote: Nathan Bossart writes: I don't mind proceeding with the patch if there is strong support for it. I wavered only because it's hard to be confident that we are choosing the right limit. I'm not that fuss

Re: First draft of PG 17 release notes

On 9/20/24 12:55 PM, Laurenz Albe wrote: On Fri, 2024-09-20 at 10:02 -0400, Jonathan S. Katz wrote: Attached is a proposal for the major features section. This borrows from the release announcement draft[1] and lists out features and themes that have broad user impact. This was a bit

Re: Should rolpassword be toastable?

On 9/20/24 1:23 AM, Michael Paquier wrote: On Thu, Sep 19, 2024 at 09:46:00PM -0500, Nathan Bossart wrote: On Thu, Sep 19, 2024 at 07:37:55PM -0400, Jonathan S. Katz wrote: Shouldn't we enforce the limit in every case in encrypt_password, not just this one? (I do agree that encrypt_pas

Re: First draft of PG 17 release notes

On 5/9/24 12:03 AM, Bruce Momjian wrote: I have committed the first draft of the PG 17 release notes; you can see the results here: release-17: 188 I welcome feedback. For some reason it was an easier job than usual. Attached is a proposal for the major features section. This borro

Re: Should rolpassword be toastable?

On 9/19/24 6:14 PM, Tom Lane wrote: Nathan Bossart writes: Oh, actually, I see that we are already validating the hash, but you can create valid SCRAM-SHA-256 hashes that are really long. You _can_, but it's up to a driver or a very determined user to do this, as it involves creating a very

Re: PostgreSQL 17 release announcement draft

On 9/7/24 6:58 PM, David Rowley wrote: On Sun, 8 Sept 2024 at 06:44, Jonathan S. Katz wrote: I've attached the latest copy. Is "This release expands on functionality both for managing data in partitions" still relevant given the MERGE/SPLIT PARTITION was reverted [1]?

Re: PostgreSQL 17 release announcement draft

On 9/6/24 2:01 PM, Matthias van de Meent wrote: I think this needs some adjustment: IIUC the new feature in PG17's 295c36c0 is that we now also track (and show) timings for local blocks. I/O timings on shared and temp blocks were already tracked (and displayed with the BUFFERS option) when track

Re: PostgreSQL 17 release announcement draft

On 9/6/24 6:40 PM, Jelte Fennema-Nio wrote: On Fri, 6 Sept 2024 at 19:04, Jonathan S. Katz wrote: Please see v2 attached. As per original note, please provide feedback before Mon, Sep 9 @ 12:00 UTC so we can begin the translation process. The following sentence was part of the beta1 release

Re: PostgreSQL 17 release announcement draft

On 9/4/24 5:04 PM, Jonathan S. Katz wrote: Hi, Attached is the draft of the PostgreSQL 17 release announcement. This is a draft of the text that will go into the press kit, with the key portions to review starting from the top of the document, up until the "About PostgreSQL&quo

PostgreSQL 17 release announcement draft

Hi, Attached is the draft of the PostgreSQL 17 release announcement. This is a draft of the text that will go into the press kit, with the key portions to review starting from the top of the document, up until the "About PostgreSQL" section. Please provide feedback on content accuracy, notab

Re: Large expressions in indexes can't be stored (non-TOASTable)

On 9/4/24 3:08 PM, Tom Lane wrote: Nathan Bossart writes: Thanks to commit 96cdeae, only a few catalogs remain that are missing TOAST tables: pg_attribute, pg_class, pg_index, pg_largeobject, and pg_largeobject_metadata. I've attached a short patch to add one for pg_index, which resolves the i

Large expressions in indexes can't be stored (non-TOASTable)

Hi, I ran into an issue (previously discussed[1]; quoting Andres out of context that not addressing it then would "[a]ll but guarantee that we'll have this discussion again"[2]) when trying to build a very large expression index that did not fit within the page boundary. The real-world use ca

Re: On disable_cost

On 8/23/24 5:33 PM, Jonathan S. Katz wrote: On 8/23/24 3:32 PM, Tom Lane wrote: Robert Haas writes: I think it's not that bad, because we can limit the knowledge of this hack to the amcostestimate interface, which doesn't really deal in "the user told us not to do it this way

Re: On disable_cost

On 8/23/24 3:32 PM, Tom Lane wrote: Robert Haas writes: I find both of your proposed solutions above to be pretty inelegant, They are that. If we were working in a green field I'd not propose such things ... but we aren't. I believe there are now a fair number of out-of-core index AMs, so I

Re: On disable_cost

On 8/23/24 2:29 PM, Robert Haas wrote: On Fri, Aug 23, 2024 at 2:20 PM Jonathan S. Katz wrote: I don't think extension maintainers necessarily have the same level of PostgreSQL internals as you or many of the other people who frequent -hackers, so I think it's fair for them to ask qu

Re: On disable_cost

On 8/23/24 1:11 PM, Robert Haas wrote: On Fri, Aug 23, 2024 at 11:17 AM Jonathan S. Katz wrote: We hit an issue with pgvector[0] where a regular `SELECT count(*) FROM table`[1] is attempting to scan the index on the vector column when `enable_seqscan` is disabled. Credit to Andrew Kane (CC&#

Re: On disable_cost

On 8/21/24 10:29 AM, Robert Haas wrote: I went ahead and committed these patches. I know there's some debate over whether we want to show the # of disabled nodes and if so whether it should be controlled by COSTS, and I suspect I haven't completely allayed David's concerns about the initial_cost

PostgreSQL 17 RC1 & GA dates

Hi, The date for PostgreSQL 17 Release Candidate 1 (RC1) is September 5, 2024. Please ensure all open items[1] are completed and committed before August 31, 2024 12:00 UTC to allow enough time for them to clear the buildfarm. The current target date for the PostgreSQL 17 GA release is Septem

Re: Add SPLIT PARTITION/MERGE PARTITIONS commands

On 8/22/24 12:33 PM, Robert Haas wrote: I think it is very unlikely that the problems mentioned above are the only ones. They're just what I found in an hour or two of testing. Even if they were, we're probably too close to release to be rushing out last minute fixes to multiple unanticipated se

Re: Conflict detection and logging in logical replication

On 8/6/24 4:15 AM, Zhijie Hou (Fujitsu) wrote: Thanks for the idea! I thought about few styles based on the suggested format, what do you think about the following ? Thanks for proposing formats. Before commenting on the specifics, I do want to ensure that we're thinking about the following f

2024-08-08 update release announcement draft

Hi, Attached is the release announcement draft for the 2024-08-08 release. Please review for accuracy and omissions, and provide feedback no later than 2024-08-08 12:00 UTC. Thanks! Jonathan The PostgreSQL Global Development Group has released an update to all supported versions of PostgreSQ

Re: Detailed release notes

On Jul 26, 2024, at 9:26 AM, Marcos Pegoraro wrote:Em sex., 26 de jul. de 2024 às 10:11, Daniel Gustafsson escreveu: That's likely the wrong level of detail for the overwhelming majority of release notes readers.  I have a feeling this was discussed not too long ago but (if so)

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: 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

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: PostgreSQL 17 Beta 1 release announcement draft

On 5/23/24 8:00 AM, Alvaro Herrera wrote: Looks good. Some minor changes: Thanks for this - right at the deadline! :D ### Query and Operational Performance Improvements PostgreSQL 17 builds on recent releases and continues to improve performance across the entire system. [Vacuum](https://

Re: PostgreSQL 17 Beta 1 release announcement draft

On 5/19/24 5:34 PM, Jonathan S. Katz wrote: 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

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

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/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 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/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 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 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/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/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/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/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 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 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/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

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: 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

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/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,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 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

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

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

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

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

Re: PostgreSQL 17 Release Management Team & Feature Freeze

On 4/8/24 8:29 AM, Andres Freund wrote: Hi, On 2024-04-08 09:26:09 -0400, Robert Haas wrote: On Sun, Apr 7, 2024 at 6:50 PM Michael Paquier wrote: And maybe we need to think of a way to further mitigate this crush of last minute commits. e.g. In the last week, you can't have more feature commi

Re: 2024-02-08 release announcement draft

On 2/6/24 3:19 AM, jian he wrote: On Tue, Feb 6, 2024 at 12:43 PM Jonathan S. Katz wrote: Hi, Attached is a draft of the 2024-02-08 release announcement. Please review for accuracy and notable omissions. Please provide any feedback no later than 2024-02-08 12:00 UTC (and preferably sooner

2024-02-08 release announcement draft

Hi, Attached is a draft of the 2024-02-08 release announcement. Please review for accuracy and notable omissions. Please provide any feedback no later than 2024-02-08 12:00 UTC (and preferably sooner). Thanks, Jonathan The PostgreSQL Global Development Group has released an update to all s

Re: heavily contended lwlocks with long wait queues scale badly

On 1/16/24 1:11 AM, Michael Paquier wrote: On Thu, Jan 11, 2024 at 09:47:33AM -0500, Jonathan S. Katz wrote: I have similar data sources to Nathan/Michael and I'm trying to avoid piling on, but one case that's interesting occurred after a major version upgrade from PG10 to PG14 on

Re: heavily contended lwlocks with long wait queues scale badly

On 1/10/24 10:45 PM, Michael Paquier wrote: On Wed, Jan 10, 2024 at 09:17:47PM -0600, Nathan Bossart wrote: Now that commit a4adc31 has had some time to bake and concerns about unintended consequences may have abated, I wanted to revive this back-patching discussion. I see a few possibly-relate

Re: Password leakage avoidance

On 1/2/24 7:23 AM, Sehrope Sarkuni wrote: Having worked on and just about wrapped up the JDBC driver patch for this, couple thoughts: 2. Password encoding should be split out and made available as its own functions. Not just as part of a wider "create _or_ alter a user's password" function at

Re: Password leakage avoidance

On 12/31/23 9:50 AM, Magnus Hagander wrote: On Wed, Dec 27, 2023 at 10:31 PM Jonathan S. Katz wrote: On 12/24/23 12:15 PM, Tom Lane wrote: Maybe we need a PQcreaterole that provide the mechanism to set passwords safely. It'd likely need to take all the options need for creating a role

Re: Password leakage avoidance

On 12/24/23 12:15 PM, Tom Lane wrote: Maybe we need a PQcreaterole that provide the mechanism to set passwords safely. It'd likely need to take all the options need for creating a role, but that would at least give the underlying mechanism to ensure we're always sending a hashed password to the

Re: Password leakage avoidance

On 12/24/23 10:14 AM, Joe Conway wrote: On 12/23/23 11:00, Tom Lane wrote: Joe Conway writes: The attached patch set moves the guts of \password from psql into the libpq client side -- PQchangePassword() (patch 0001). Haven't really read the patch, just looked at the docs, but here's a bit o

Re: 2023-11-09 release announcement draft

On 11/6/23 9:52 PM, Noah Misch wrote: On Mon, Nov 06, 2023 at 05:04:25PM -0500, Jonathan S. Katz wrote: The PostgreSQL Global Development Group has released an update to all supported versions of PostgreSQL, including 16.1, 15.5, 14.10, 13.13, 12.17, and 11.22 This release fixes over 55 bugs

2023-11-09 release announcement draft

Hi, Attached is the release announcement draft for the 2023-11-09 release (16.1 et al.). Please review for accuracy and notable omissions. Please have all feedback in by 2023-11-09 08:00 UTC at the latest (albeit the sooner the better). Thanks, Jonathan The PostgreSQL Global Development G

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: 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

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 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 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 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 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/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 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

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

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

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

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 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/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/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

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: [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

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: 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

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: plan_create_index_workers doesn't account for TOAST

On 6/29/23 10:12 AM, Jonathan S. Katz wrote: Hi, plan_create_index_workers[1] does not consider the amount of tuples existing in TOAST pages when determining the number of parallel workers to use for a build. The estimation comes from estimate_rel_size[2], which in this case, will just take

plan_create_index_workers doesn't account for TOAST

Hi, plan_create_index_workers[1] does not consider the amount of tuples existing in TOAST pages when determining the number of parallel workers to use for a build. The estimation comes from estimate_rel_size[2], which in this case, will just take the value from rel->rd_rel->relpages. We prob

Re: PostgreSQL 16 Beta 2 release announcement draft

On 6/27/23 12:54 PM, Roberto Mello wrote: On Tue, Jun 27, 2023 at 8:32 AM Jonathan S. Katz wrote: I used the open items list[1] to build the draft. If there are any notable please omissions, please let me know. I noticed that ldap_password_hook [1] was omitted from the release notes. I

PostgreSQL 16 Beta 2 release announcement draft

Hi, Please see the attached draft of the PostgreSQL 16 Beta 2 release announcement. I used the open items list[1] to build the draft. If there are any notable please omissions, please let me know. Please leave all feedback by June 29, 0:00 AoE. Thanks, Jonathan [1] https://wiki.postgresq

  1   2   3   4   5   6   7   >