Re: Having postgresql.org link to cgit instead of gitweb

On 9/22/25 11:27 AM, Álvaro Herrera wrote: On 2025-Sep-22, Tom Lane wrote: My first thought about scheduling was "best not in the middle of the 18.0 release cycle". However, I don't know of any actual connection between gitweb/cgit and the release-making tasks. My second thought was "the poin

Re: Having postgresql.org link to cgit instead of gitweb

On 9/19/25 4:54 PM, Jonathan S. Katz wrote: On 9/19/25 4:14 PM, Tom Lane wrote: "Jonathan S. Katz" writes: On a quick read, I believe this is easily settable in the cgit.css file by setting "tab-size" to "4". I did a quick test hacking this inline, and it work

Re: PostgreSQL 18 GA press release draft

On 9/9/25 11:13 PM, Jonathan S. Katz wrote: Hi, Attached is a draft of the PostgreSQL 18 GA press release. A few comments before the ask for reviewing: * I still need to write up the theme and the quote, which I'll provide tomorrow after hearing the first round of feedback * The relea

Re: Having postgresql.org link to cgit instead of gitweb

On 9/19/25 12:17 PM, Tom Lane wrote: Peter Geoghegan writes: cgit messes up indentation by showing 8 space tabs (not 4 space tabs) -- that's certainly not ideal. To me that seems like a complete blocker for this proposal, if we can't find a fix. On a quick read, I believe this is easily set

Re: PG 18 relnotes and RC1

On 9/19/25 12:50 PM, Nathan Bossart wrote: On Fri, Sep 19, 2025 at 09:25:52AM -0500, Nathan Bossart wrote: I'm hoping to commit this around 20:00 UTC today, and I will be happy to address any feedback that folks have in the meantime. Here's a v4. The content is the same except for a typo fix,

Re: Having postgresql.org link to cgit instead of gitweb

On 9/19/25 4:14 PM, Tom Lane wrote: "Jonathan S. Katz" writes: On a quick read, I believe this is easily settable in the cgit.css file by setting "tab-size" to "4". I did a quick test hacking this inline, and it worked. Cool, thanks for looking into it. Te

Re: Having postgresql.org link to cgit instead of gitweb

On 9/19/25 7:42 AM, David Rowley wrote: On Fri, 19 Sept 2025 at 23:05, Peter Eisentraut wrote: On 19.09.25 10:22, Álvaro Herrera wrote: There are two things we could do. One is to simply restrict `git blame` to authenticated users; this shouldn't be_too_ bad. But if we don't want that, we c

Re: PG 18 relnotes and RC1

On 9/19/25 4:09 PM, Nathan Bossart wrote: Committed. Thanks! Jonathan OpenPGP_signature.asc Description: OpenPGP digital signature

Re: Having postgresql.org link to cgit instead of gitweb

On 9/19/25 10:47 AM, Álvaro Herrera wrote: On 2025-Sep-19, Peter Eisentraut wrote: On 19.09.25 03:12, Jonathan S. Katz wrote: * Moves any web links to git.postgresql.org repos to use the cgit interface instead of gitweb (e.g. [1]) * Update the commit search[2] to use cgit instead of gitweb

Having postgresql.org link to cgit instead of gitweb

Sep 17 00:00:00 2001 From: "Jonathan S. Katz" Date: Thu, 18 Sep 2025 21:02:40 -0400 Subject: [PATCH] Move gitweb links to cgit Parts of the gitweb functionality are no longer accessible, specifically viewing individual commits. cgit doesn't have this issue, thus move the website l

Re: PG 18 relnotes and RC1

On 9/18/25 3:32 PM, Nathan Bossart wrote: On Thu, Sep 18, 2025 at 03:25:08PM -0400, Robert Haas wrote: As I see it, while our feature freeze isn't perfect -- mostly because too many things get slipped in at the last minute that aren't really in great shape -- it's a lot better than the old proce

Re: PG 18 relnotes and RC1

On 9/18/25 3:25 PM, Robert Haas wrote: On Thu, Sep 18, 2025 at 2:19 PM Jonathan S. Katz wrote: Glad to hear I've been doing my job backwards for years ;) That said, I am always willing to learn how to improve the process. I don't really care for the flip tone here. I didn't

Re: PG 18 relnotes and RC1

On 9/18/25 2:33 PM, Jonathan S. Katz wrote: On 9/18/25 2:19 PM, Nathan Bossart wrote: Quick analysis of the differences: Common: * AIO * skip scan * pg_upgrade * UUIDv7 * virtual generated columns * OAuth Only v1 (my patch): * OLD/NEW for

Re: PG 18 relnotes and RC1

On 9/18/25 2:19 PM, Nathan Bossart wrote: On Thu, Sep 18, 2025 at 01:38:44PM -0400, Robert Haas wrote: That seems completely backwards to me. We should go with the version that was submitted weeks ago and upon which people have had the opportunity to comment unless you can justify each change th

Re: PG 18 relnotes and RC1

On 9/18/25 1:38 PM, Robert Haas wrote: On Thu, Sep 18, 2025 at 12:59 PM Jonathan S. Katz wrote: I like Nathan's version better. I suggest we go with that one. Why? This seems arbitrary without more details. I’ve spent the past several weeks staring at the release notes, talking to

Re: PG 18 relnotes and RC1

> On Sep 18, 2025, at 12:20 PM, Robert Haas wrote: > > On Thu, Sep 18, 2025 at 12:09 PM Jonathan S. Katz > wrote: >> Please see attached draft for the major features of PostgreSQL 18. > > I like Nathan's version better. I suggest we go with that one. Why?

Re: PG 18 relnotes and RC1

On 9/17/25 2:51 PM, Jonathan S. Katz wrote: On Sep 17, 2025, at 2:47 PM, Peter Eisentraut wrote: On 31.08.25 05:02, Nathan Bossart wrote: On Sat, Aug 30, 2025 at 05:56:12PM -0400, Bruce Momjian wrote: On Sat, Aug 30, 2025 at 03:02:10PM -0500, Nathan Bossart wrote: The 18beta1 announcement

Re: PG 18 relnotes and RC1

> On Sep 17, 2025, at 2:47 PM, Peter Eisentraut wrote: > > On 31.08.25 05:02, Nathan Bossart wrote: >>> On Sat, Aug 30, 2025 at 05:56:12PM -0400, Bruce Momjian wrote: >>> On Sat, Aug 30, 2025 at 03:02:10PM -0500, Nathan Bossart wrote: The 18beta1 announcement [0] has a good list, too. *f

Re: PostgreSQL 18 GA press release draft

On 9/12/25 11:46 AM, Jonathan S. Katz wrote: As per above, I'll need remaining feedback no later than 2025-09-14 0:00 UTC - after this, it's frozen for the translation process to begin. Thank everyone for your feedback. I've attached the copy of the release announceme

Re: PostgreSQL 18 GA press release draft

On 9/12/25 3:24 PM, Álvaro Herrera wrote: Hello, Thanks for putting this together! It's quite the monster. I read through and found the following points worth mentioning: Thank you! I think almost all of the non-stock section titles Are Lacking Case Title. Putting this is as an example o

Re: PostgreSQL 18 GA press release draft

On 9/12/25 1:11 PM, Jeff Davis wrote: On Tue, 2025-09-09 at 23:13 -0400, Jonathan S. Katz wrote: Hi, Attached is a draft of the PostgreSQL 18 GA press release. A few comments before the ask for reviewing: "This release adds the [`PG_UNICODE_FAST`], which accelerates lookups using the `

Re: PostgreSQL 18 GA press release draft

On 9/12/25 2:18 PM, Masahiko Sawada wrote: I found a typo; s/gen_rand_uuid()/gen_random_uuid()/ Good catch - thanks! Jonathan OpenPGP_signature.asc Description: OpenPGP digital signature

Re: PostgreSQL 18 GA press release draft

On 9/10/25 3:59 PM, Peter Geoghegan wrote: "It can also automatically transform queries with `OR` constructs in their `WHERE` clause into a logically equivalent IN() representation that can be pushed down to index scan nodes, leading to significantly faster execution". Thanks for the detailed

Re: PostgreSQL 18 GA press release draft

On 9/10/25 9:52 AM, John Naylor wrote: On Wed, Sep 10, 2025 at 10:13 AM Jonathan S. Katz wrote: PostgreSQL 18 also supports using x86 AVX-512 instructions for CRC32 calculations, which are used in page checksums and are also available in the new [`crc32`](https://www.postgresql.org/docs/18

Re: PostgreSQL 18 GA press release draft

On 9/10/25 2:58 AM, Jakub Wartak wrote: and just leave it as "Finally, PostgreSQL 18 adds basic [NUMA observability]" ? Rationale: for every other software that I saw NUMA awareness reference was always linked to gaining performance , but just linking against libnuma is not giving us this. Hm

Re: PostgreSQL 18 GA press release draft

On 9/10/25 12:29 AM, jian he wrote: On Wed, Sep 10, 2025 at 11:13 AM Jonathan S. Katz wrote: Hi, Please review for the press release for the following: * Correctness and accuracy of what's described - we want to be technically correct, but we also need to explain why something matte

Re: PostgreSQL 18 GA press release draft

On 9/9/25 11:38 PM, Peter Smith wrote: FWIW, here are a couple of AI-detected issues. This typo: "with contains installers" should be "which contains installers" Thanks! This potential mismatch: "Built on over 35 years of engineering" is inconsistent with the earlier "nearly 30 years" statem

PostgreSQL 18 GA press release draft

Hi, Attached is a draft of the PostgreSQL 18 GA press release. A few comments before the ask for reviewing: * I still need to write up the theme and the quote, which I'll provide tomorrow after hearing the first round of feedback * The release is a bit long - this is due in part to what I thi

Re: PG 18 relnotes and RC1

> On Aug 30, 2025, at 5:56 PM, Bruce Momjian wrote: > > On Sat, Aug 30, 2025 at 03:02:10PM -0500, Nathan Bossart wrote: >>> On Sat, Aug 30, 2025 at 02:42:47PM -0500, Nathan Bossart wrote: >>> On Sat, Aug 30, 2025 at 01:51:23PM -0500, Nathan Bossart wrote: AFAIK nobody has started on the "

Re: PostgreSQL 18 Beta 1 release announcement draft

On 5/7/25 5:16 PM, Jacob Champion wrote: On Tue, May 6, 2025 at 8:46 PM Jonathan S. Katz wrote: Here's the next update Thanks! PostgreSQL 18 introduces `oauth` authentication, which people can create extensions that support OAuth 2.0 based authentication mechanisms that PostgreSQ

Re: PostgreSQL 18 Beta 1 release announcement draft

On 5/7/25 4:54 PM, Bruce Momjian wrote: On Tue, May 6, 2025 at 11:24:44PM -0400, Jonathan Katz wrote: On 5/6/25 11:17 AM, Nathan Bossart wrote: IMHO we should emphasize that MD5 password support will be removed in a future release and that users should migrate to something else soon. I'm ima

Re: PostgreSQL 18 Beta 1 release announcement draft

On 5/7/25 5:38 AM, Matthias van de Meent wrote: On Mon, 5 May 2025 at 21:07, Jonathan S. Katz wrote: Hi, Attached is a draft of the PostgreSQL 18 Beta 1 release announcement. The goal of this announcement is to introduce the new capabilities planned for PostgreSQL 18 and give users an idea

Re: PostgreSQL 18 Beta 1 release announcement draft

On 5/7/25 5:18 AM, Jelte Fennema-Nio wrote: On Mon, 5 May 2025 at 21:07, Jonathan S. Katz wrote: Attached is a draft of the PostgreSQL 18 Beta 1 release announcement. It might make sense to add a small sentence like "this release introduces version 3.2 of the wire protocol, but libpq

Re: PostgreSQL 18 Beta 1 release announcement draft

On 5/6/25 9:15 AM, Álvaro Herrera wrote: On 2025-May-05, Jonathan S. Katz wrote: ### Other Highlights Starting with PostgreSQL 18, data checksums, which are used to validate the integrity of stored data, are now enabled by default on new PostgreSQL clusters. You can choose to disable this

Re: PostgreSQL 18 Beta 1 release announcement draft

On 5/6/25 11:55 AM, Andres Freund wrote: Hi, On 2025-05-05 15:07:01 -0400, Jonathan S. Katz wrote: ### Performance PostgreSQL 18 introduces an asynchronous I/O (AIO) subsystem using `io_uring` on Linux, which, when combined with direct I/O (DIO), lets PostgreSQL directly interface with

Re: PostgreSQL 18 Beta 1 release announcement draft

On 5/6/25 11:17 AM, Nathan Bossart wrote: IMHO we should emphasize that MD5 password support will be removed in a future release and that users should migrate to something else soon. I'm imagining it'll still be at least a couple of years before I muster up the courage to actually propose remov

Re: 2025-05-08 release announcement draft

On 5/6/25 8:29 AM, Matthias van de Meent wrote: On Tue, 6 May 2025 at 05:32, Jonathan S. Katz wrote: Hi, Attached is the draft of the release announcement for the 2025-05-08 release. Please review for correctness and omissions. Please provide feedback no later than 2025-05-08 12:00 UTC. I

Re: 2025-05-08 release announcement draft

On 5/6/25 5:23 AM, jian he wrote: On Tue, May 6, 2025 at 11:32 AM Jonathan S. Katz wrote: Hi, Attached is the draft of the release announcement for the 2025-05-08 release. Please review for correctness and omissions. Please provide feedback no later than 2025-05-08 12:00 UTC. * Prevent

2025-05-08 release announcement draft

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

PostgreSQL 18 Beta 1 release announcement draft

Hi, Attached is a draft of the PostgreSQL 18 Beta 1 release announcement. The goal of this announcement is to introduce the new capabilities planned for PostgreSQL 18 and give users an idea of areas we'd like to see tested. Please check for accuracy and if there are glaring omissions (happy

Re: PG 18 release notes draft committed

On 5/3/25 7:48 PM, Alexander Borisov wrote: 04.05.2025 02:28, Bruce Momjian wrote: It doesn't warrant its own item because it is not user-facing work.  The best we can do is add the commit to an existing item and add you as a co-author on an existing item.  You will see several items that a

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

  1   2   3   4   5   6   7   8   >