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.

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

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 adds an interface

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"

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

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 logically

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 view

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

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'd say

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

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

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 the way

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

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

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

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

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/

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

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

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 a database

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

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

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

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

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.

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

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`)

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 performance

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,

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

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

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

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 fixed both instances. Thanks!

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

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

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

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

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]

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.

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

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

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]

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

On 6/23/23 12:16 PM, Tom Lane wrote: "David G. Johnston" writes: On Thu, Jun 22, 2023 at 5:08 PM Tom Lane wrote: * I agree that the "tabular" format looks nicer and has fewer i18n issues than the other proposals. As you are on board with a separate command please clarify whether you mean

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

On 6/23/23 11:52 AM, David G. Johnston wrote: On Thu, Jun 22, 2023 at 5:08 PM Tom Lane <mailto:t...@sss.pgh.pa.us>> wrote: "Jonathan S. Katz" mailto:jk...@postgresql.org>> writes: > On 6/15/23 2:47 PM, David G. Johnston wrote: >> Robert -

Re: collation-related loose ends before beta2

On 6/20/23 5:02 AM, Jeff Davis wrote: Status on collation loose ends: 1. There's an open item "Switch to ICU for 17". It's a little bit confusing exactly what that means, and the CF entry refers to two items, one of which is the build-time default to --with-icu. As far as I know, building with

Re: EBCDIC sorting as a use case for ICU rules

On 6/21/23 12:14 PM, Jeff Davis wrote: On Wed, 2023-06-21 at 15:28 +0200, Daniel Verite wrote: At a conference this week I was asked if ICU could be able to sort like EBCDIC [2]. It turns out it has been already  asked on -general a few years ago [3] with no satisfactory answer at the time ,

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

On 6/15/23 2:47 PM, David G. Johnston wrote: Robert - can you please comment on what you are willing to commit in order to close out your open item here.  My take is that the design for this, the tabular form a couple of emails ago (copied here), is ready-to-commit, just needing the actual

PostgreSQL 16 Beta 2 Release Date

Hi, The release date for PostgreSQL 16 Beta 2 is June 29, 2023. Please be sure to commit any open items[1] for the Beta 2 release before June 25, 2023 0:00 AoE[2] to give them enough time to work through the buildfarm. Thanks, Jonathan [1]

Re: Order changes in PG16 since ICU introduction

On 6/6/23 3:56 PM, Joe Conway wrote: On 6/6/23 15:55, Tom Lane wrote: Robert Haas writes: On Tue, Jun 6, 2023 at 3:25 PM Tom Lane wrote: Also +1, except that I find "none" a rather confusing choice of name. There *is* a provider, it's just PG itself not either libc or ICU. I thought Joe's

Re: Let's make PostgreSQL multi-threaded

On 6/5/23 11:33 AM, Heikki Linnakangas wrote: On 05/06/2023 11:18, Tom Lane wrote: Heikki Linnakangas writes: I spoke with some folks at PGCon about making PostgreSQL multi-threaded, so that the whole server runs in a single process, with multiple threads. It has been discussed many times in

Re: Docs: Encourage strong server verification with SCRAM

On 6/5/23 11:22 AM, Jacob Champion wrote: On Sat, Jun 3, 2023 at 2:50 PM Michael Paquier wrote: Took me some time to get back to it, but applied this way. Thanks all! +1; thank you! Jonathan OpenPGP_signature Description: OpenPGP digital signature

Re: Docs: Encourage strong server verification with SCRAM

On 5/26/23 6:47 PM, Jacob Champion wrote: On Thu, May 25, 2023 at 6:10 PM Jonathan S. Katz wrote: + To prevent server spoofing from occurring when using + scram-sha-256 password authentication + over a network, you should ensure you are connecting using SSL. seems to backtrack

Re: vector search support

On 4/26/23 9:31 AM, Giuseppe Broccolo wrote: Hi Nathan, I find the patches really interesting. Personally, as Data/MLOps Engineer, I'm involved in a project where we use embedding techniques to generate vectors from documents, and use clustering and kNN searches to find similar documents

Re: vector search support

On 5/25/23 1:48 PM, Oliver Rice wrote: A nice side effect of using the float8[] to represent vectors is that it allows for vectors of different sizes to coexist in the same column. We most frequently see (pgvector) vector columns being used for storing ML embeddings. Given that different

Re: vector search support

Hi, On 4/21/23 8:07 PM, Nathan Bossart wrote: Attached is a proof-of-concept/work-in-progress patch set that adds functions for "vectors" repreѕented with one-dimensional float8 arrays. These functions may be used in a variety of applications, but I am proposing them with the AI/ML use-cases in

Re: Docs: Encourage strong server verification with SCRAM

On 5/25/23 3:27 PM, Jacob Champion wrote: On Thu, May 25, 2023 at 10:48 AM Jonathan S. Katz wrote: Overall, +1 to tightening the language around the docs in this area. However, to paraphrase Stephen, I think the language, as currently written, makes the problem sound scarier than it actually

Re: Docs: Encourage strong server verification with SCRAM

On 5/25/23 1:29 PM, Stephen Frost wrote: Greetings, * Jacob Champion (jchamp...@timescale.com) wrote: On 5/24/23 05:04, Daniel Gustafsson wrote: On 23 May 2023, at 23:02, Stephen Frost wrote: Perhaps more succinctly- maybe we should be making adjustments to the current language instead of

Re: PostgreSQL 16 Beta 1 release announcement draft

On 5/25/23 12:16 AM, Andres Freund wrote: Hi, On 2023-05-24 23:30:58 -0400, Jonathan S. Katz wrote: Ah, OK, that's why I didn't grok it. I read through the first message in[1] and definitely agree it should be in the announcement. How about: "PostgreSQL 16 also shows up to a 300% improv

Re: PostgreSQL 16 Beta 1 release announcement draft

On 5/24/23 11:30 PM, Jonathan S. Katz wrote: On 5/24/23 9:20 PM, Jonathan S. Katz wrote: I currently have it as the below in the release announcement. If it you send any suggested updates, I can try to put them in before release: PostgreSQL 16 can also improve the performance of concurrent

Re: PostgreSQL 16 Beta 1 release announcement draft

On 5/24/23 9:20 PM, Jonathan S. Katz wrote: On 5/24/23 8:04 PM, Andres Freund wrote: Hi, On 2023-05-24 19:57:39 -0400, Jonathan S. Katz wrote: On 5/24/23 5:28 PM, Andres Freund wrote: I think the relation extension improvements ought to be mentioned here as well? Up to 3x faster

Re: PostgreSQL 16 Beta 1 release announcement draft

On 5/24/23 8:04 PM, Andres Freund wrote: Hi, On 2023-05-24 19:57:39 -0400, Jonathan S. Katz wrote: On 5/24/23 5:28 PM, Andres Freund wrote: I think the relation extension improvements ought to be mentioned here as well? Up to 3x faster concurrent data load with COPY seems practically

Re: PostgreSQL 16 Beta 1 release announcement draft

On 5/24/23 5:28 PM, Andres Freund wrote: I think the relation extension improvements ought to be mentioned here as well? Up to 3x faster concurrent data load with COPY seems practically relevant. I missed that -- not sure I'm finding it in the release notes with a quick grep -- which

Re: PostgreSQL 16 Beta 1 release announcement draft

On 5/22/23 3:23 PM, Erik Rijkers wrote: Op 5/21/23 om 19:07 schreef Jonathan S. Katz: On 5/19/23 12:17 AM, Jonathan S. Katz wrote: Hi, Attached is a draft of the release announcement for PostgreSQL 16 Beta Please provide feedback no later than May 24, 0:00 AoE. This will give Thanks

Re: PG 16 draft release notes ready

On 5/24/23 12:13 AM, David Rowley wrote: On Wed, 24 May 2023 at 15:54, Bruce Momjian wrote: On Wed, May 24, 2023 at 08:37:45AM +1200, David Rowley wrote: On Mon, 22 May 2023 at 07:05, Jonathan S. Katz wrote: * Parallel execution of queries that use `FULL` and `OUTER` joins I think

Re: PG 16 draft release notes ready

On 5/22/23 4:18 PM, Robert Haas wrote: On Sun, May 21, 2023 at 3:05 PM Jonathan S. Katz wrote: * Support for regular expressions for matching usernames and databases names in `pg_hba.conf`, and user names in `pg_ident.conf` I suggest that this is not a major feature. Perhaps the work that I

Re: PG 16 draft release notes ready

On 5/23/23 4:37 PM, David Rowley wrote: On Mon, 22 May 2023 at 07:05, Jonathan S. Katz wrote: * Parallel execution of queries that use `FULL` and `OUTER` joins I think this should be `RIGHT` joins rather than `OUTER` joins. LEFT joins have been parallelizable I think for a long time now

Re: PG 16 draft release notes ready

On 5/21/23 3:04 PM, Jonathan S. Katz wrote: On 5/18/23 4:49 PM, Bruce Momjian wrote: I have completed the first draft of the PG 16 release notes. One thing that we could attempt for this beta is to include a prospective list of "major features + enhancements." Of course it can cha

Re: PG 16 draft release notes ready

On 5/21/23 3:24 PM, Andres Freund wrote: Hi, On May 21, 2023 11:46:56 AM PDT, "Jonathan S. Katz" wrote: On 5/21/23 1:13 PM, Andres Freund wrote: Looking through the release notes, I didn't see an entry for commit c6e0fe1f2a08505544c410f613839664eea9eb21 Author: David Rowley Da

Re: PG 16 draft release notes ready

On 5/18/23 4:49 PM, Bruce Momjian wrote: I have completed the first draft of the PG 16 release notes. One thing that we could attempt for this beta is to include a prospective list of "major features + enhancements." Of course it can change before the GA, but it'll give readers some idea of

Re: PG 16 draft release notes ready

On 5/21/23 1:13 PM, Andres Freund wrote: Looking through the release notes, I didn't see an entry for commit c6e0fe1f2a08505544c410f613839664eea9eb21 Author: David Rowley Date: 2022-08-29 17:15:00 +1200 Improve performance of and reduce overheads of memory management even though

Re: PostgreSQL 16 Beta 1 release announcement draft

On 5/19/23 12:17 AM, Jonathan S. Katz wrote: Hi, Attached is a draft of the release announcement for PostgreSQL 16 Beta 1. The goal of this announcement is to get people excited about testing the beta and highlight many of the new features. Please review for inaccuracies, omissions

Re: PostgreSQL 16 Beta 1 release announcement draft

On 5/19/23 10:57 AM, Nathan Bossart wrote: On Fri, May 19, 2023 at 12:17:50AM -0400, Jonathan S. Katz wrote: PostgreSQL 16 continues to give users to the ability grant privileged access to features without requiring superuser with new [predefined roles](https://www.postgresql.org/docs/devel

Re: PostgreSQL 16 Beta 1 release announcement draft

On 5/19/23 1:42 AM, Erik Rijkers wrote: Op 5/19/23 om 06:17 schreef Jonathan S. Katz: Hi, Attached is a draft of the release announcement for PostgreSQL 16 Beta Hi, The usual small fry: 'continues to to'  should be 'continues to' 'continues to give users to the ability'  should

PostgreSQL 16 Beta 1 release announcement draft

Hi, Attached is a draft of the release announcement for PostgreSQL 16 Beta 1. The goal of this announcement is to get people excited about testing the beta and highlight many of the new features. Please review for inaccuracies, omissions, and other suggestions / errors. Please provide

Re: PG 16 draft release notes ready

On 5/18/23 4:49 PM, Bruce Momjian wrote: I have completed the first draft of the PG 16 release notes. You can see the output here: https://momjian.us/pgsql_docs/release-16.html I will adjust it to the feedback I receive; that URL will quickly show all updates. Still reading, but

Re: PG 16 draft release notes ready

On 5/18/23 4:49 PM, Bruce Momjian wrote: I have completed the first draft of the PG 16 release notes. You can see the output here: https://momjian.us/pgsql_docs/release-16.html I will adjust it to the feedback I receive; that URL will quickly show all updates. Thanks for going

Re: Order changes in PG16 since ICU introduction

On 5/18/23 1:55 PM, Jeff Davis wrote: On Wed, 2023-05-17 at 19:59 -0400, Jonathan S. Katz wrote: I did a quicker read through this time. LGTM overall. I like what you did with the explanations around sensitivity (now it makes sense). Committed, thank you. \o/ There are a few things I

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

On 5/7/23 3:14 PM, Pavel Luzanov wrote: On 05.05.2023 19:51, David G. Johnston wrote: But if it is really a blocker then maybe we should produce 3 separate newline separated columns, one for the member of role, one for the list of attributes, and one with the grantor.  The column headers can

Re: Order changes in PG16 since ICU introduction

On 5/17/23 6:59 PM, Jeff Davis wrote: On Tue, 2023-05-16 at 20:23 -0700, Jeff Davis wrote: Other than that, and I took your suggestions almost verbatim. Patch attached. Thank you! Attached new patch with a typo fix and a few other edits. I plan to commit soon. I did a quicker read through

Re: Possible regression setting GUCs on \connect

On 5/17/23 1:30 PM, Alexander Korotkov wrote: Tom, On Wed, May 17, 2023 at 3:08 PM Tom Lane wrote: Amit Kapila writes: Tom/Nathan, do you have any further suggestions here? My recommendation is to revert this feature. I do not see any way that we won't regret it as a poor design. I

  1   2   3   4   5   6   7   >