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/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: SQL/JSON features for v15

Hi, On 8/15/22 10:14 PM, Andres Freund wrote: I pushed a few cleanups to https://github.com/anarazel/postgres/commits/json while I was hacking on this (ignore that it's based on the meson tree, that's just faster for me). Some of them might not be applicable anymore, but it might still make sen

Re: SQL/JSON features for v15

Hi, On 8/17/22 11:45 PM, Nikita Glukhov wrote: Hi, On 17.08.2022 04:45, Jonathan S. Katz wrote: On 8/15/22 10:14 PM, Andres Freund wrote: I pushed a few cleanups to https://github.com/anarazel/postgres/commits/json while I was hacking on this (ignore that it's based on the meson

Re: SQL/JSON features for v15

On 8/19/22 10:11 AM, Jonathan S. Katz wrote: Hi, On 8/17/22 11:45 PM, Nikita Glukhov wrote: Hi, On 17.08.2022 04:45, Jonathan S. Katz wrote: On 8/15/22 10:14 PM, Andres Freund wrote: I pushed a few cleanups to https://github.com/anarazel/postgres/commits/json while I was hacking on this

Re: SQL/JSON features for v15

On 8/23/22 12:13 AM, Michael Paquier wrote: On Mon, Aug 22, 2022 at 07:57:29PM -0700, Andres Freund wrote: To me it feels like there's a probably too much work here to cram it at this point. If several other committers shared the load of working on this it'd perhaps be doable, but I've not seen

Re: SQL/JSON features for v15

On 8/23/22 11:08 AM, Tom Lane wrote: Robert Haas writes: At the end of the day, the RMT is going to have to take a call here. It seems to me that Andres's concerns about code quality and lack of comments are probably somewhat legitimate, and in particular I do not think the use of subtransactio

Re: SQL/JSON features for v15

On 8/23/22 2:10 PM, Andrew Dunstan wrote: On 2022-08-23 Tu 13:24, Tom Lane wrote: "Jonathan S. Katz" writes: I saw Andrew suggest that the controversial parts of the patchset may be severable from some of the new functionality, so I would like to see that proposal and if it is

Re: SQL/JSON features for v15

On 8/23/22 1:26 PM, Andres Freund wrote: Hi, On 2022-08-23 13:18:49 -0400, Jonathan S. Katz wrote: Taking RMT hat off, if the outcome is "revert", I do want to ensure we don't lose momentum on getting this into v16. I know a lot of time and effort has gone into this featureset

PostgreSQL 15 Beta 4

Hi, We will be releasing a PostgreSQL 15 Beta 4 on September 8, 2022. Please have open items[1] completed and committed no later than September 5, 2022 0:00 AoE[2]. Thanks, Jonathan [1] https://wiki.postgresql.org/wiki/PostgreSQL_15_Open_Items [2] https://en.wikipedia.org/wiki/Anywhere_on_E

Re: SQL/JSON features for v15

On 8/24/22 8:16 PM, Andrew Dunstan wrote: On 2022-08-24 We 20:05, Nikita Glukhov wrote: v8 - is a highly WIP patch, which I failed to finish today. Even some test cases fail now, and they simply show unfinished things like casts to bytea (they can be simply removed) and missing safe input fun

Re: SQL/JSON features for v15

On 8/26/22 4:36 PM, Andrew Dunstan wrote: On 2022-08-26 Fr 16:11, Nikita Glukhov wrote: Hi, On 26.08.2022 22:25, Andrew Dunstan wrote: On 2022-08-24 We 20:05, Nikita Glukhov wrote: v8 - is a highly WIP patch, which I failed to finish today. Even some test cases fail now, and they simply sho

Re: SQL/JSON features for v15

On 8/29/22 8:56 AM, Amit Langote wrote: On Sat, Aug 27, 2022 at 5:11 AM Nikita Glukhov wrote: I am not sure if it's OK to eval_const_expressions() on a Query sub-expression during parse-analysis. IIUC, it is only correct to apply it to after the rewriting phase. Maybe it would be bette

Re: POC: GROUP BY optimization

On 8/18/22 3:29 AM, Tomas Vondra wrote: On 8/18/22 03:32, David Rowley wrote: Here are a couple of patches to demo the idea. Yeah, that's an option too. I should have mentioned it along with the cpu_operator_cost. BTW would you mind taking a look at the costing? I think it's fine, but it

Re: SQL/JSON features for v15

On 8/30/22 9:16 AM, Andrew Dunstan wrote: On 2022-08-30 Tu 06:29, Amit Langote wrote: On Tue, Aug 30, 2022 at 6:19 PM Alvaro Herrera wrote: On 2022-Aug-30, Amit Langote wrote: Patches 0001-0006: Yeah, these add the overhead of an extra function call (typin() -> typin_opt_error()) in possib

PostgreSQL 15 release announcement draft

Hi, Please see the first draft for the PostgreSQL 15 release announcement. This is the announcement that goes out when we ship 15.0. A few notes on the first draft: 1. I have not put in any links yet -- I want to ensure the document is close to being static before I add those in. 2. I have

Re: SQL/JSON features for v15

On 8/31/22 8:38 AM, Andrew Dunstan wrote: On 2022-08-31 We 07:01, Amit Langote wrote: On Wed, Aug 31, 2022 at 3:51 PM Amit Langote wrote: SELECT JSON_VALUE(jsonb '"aaa"', '$' RETURNING int DEFAULT 111 ON ERROR); - json_value - -111 -(1 row) - +ERROR: syntax error at or

Re: SQL/JSON features for v15

On 8/31/22 12:26 PM, Robert Haas wrote: On Wed, Aug 31, 2022 at 10:20 AM Jonathan S. Katz wrote: Andres, Robert, Tom: With this recent work, have any of your opinions changed on including SQL/JSON in v15? No. Nothing's been committed, and there's no time to review anything in d

Re: SQL/JSON features for v15

On 8/31/22 3:08 PM, Andrew Dunstan wrote: On 2022-08-31 We 14:45, Tom Lane wrote: To the extent that there was a management failure here, it was that we didn't press for a resolution sooner. Given the scale of the concerns raised in June, I kind of agree with Andres' opinion that fixing them p

Re: POC: GROUP BY optimization

On 9/1/22 9:06 AM, Tomas Vondra wrote: On 8/30/22 15:15, Jonathan S. Katz wrote: On 8/18/22 3:29 AM, Tomas Vondra wrote: On 8/18/22 03:32, David Rowley wrote: Here are a couple of patches to demo the idea. Yeah, that's an option too. I should have mentioned it along wit

Re: SQL/JSON features for v15

On 9/1/22 5:13 PM, Andrew Dunstan wrote: On 2022-08-31 We 14:22, Andrew Dunstan wrote: On 2022-08-31 We 12:48, Jonathan S. Katz wrote: With RMT hat on -- Andrew can you please revert the patchset? :-( Yes, I'll do it, starting with the v15 branch. Might take a day or so. done

Re: PostgreSQL 15 release announcement draft

On 8/31/22 1:51 PM, Michael Banck wrote: Hi, On Tue, Aug 30, 2022 at 03:58:48PM -0400, Jonathan S. Katz wrote: ### Other Notable Changes PostgreSQL server-level statistics are now collected in shared memory, eliminating the statistics collector process and writing these stats to disk

Re: PostgreSQL 15 release announcement draft

On 8/31/22 8:15 PM, Justin Pryzby wrote: On Tue, Aug 30, 2022 at 03:58:48PM -0400, Jonathan S. Katz wrote: In this latest release, PostgreSQL improves on its in-memory and on-disk sorting algorithms, with benchmarks showing speedups of 25% - 400% based on sort types. rather than "bas

Re: First draft of the PG 15 release notes

On 5/10/22 11:44 AM, Bruce Momjian wrote: I have completed the first draft of the PG 15 release notes I assume there will be major adjustments in the next few weeks based on feedback. I wanted to propose the "major enhancements" section to see if we can get an iteration in prior to Beta 4.

Re: POC: GROUP BY optimization

On 9/4/22 6:14 PM, Tomas Vondra wrote: I've pushed the fix to 15+master. In the end I just used David's patches that set parallel_setup_cost to 0. Thanks! I have closed the open item. Jonathan OpenPGP_signature Description: OpenPGP digital signature

Re: pg15b3: recovery fails with wal prefetch enabled

On 9/5/22 7:18 PM, Thomas Munro wrote: On Mon, Sep 5, 2022 at 9:08 PM Thomas Munro wrote: At Mon, 05 Sep 2022 14:15:27 +0900 (JST), Kyotaro Horiguchi wrote in At Mon, 5 Sep 2022 16:54:07 +1200, Thomas Munro wrote in On reflection, it'd be better not to clobber any pre-existing error there,

Re: pg15b3: recovery fails with wal prefetch enabled

On 9/5/22 10:03 PM, Thomas Munro wrote: On Tue, Sep 6, 2022 at 1:51 PM Tom Lane wrote: "Jonathan S. Katz" writes: On 9/5/22 7:18 PM, Thomas Munro wrote: Well I was about to commit this, but beta4 just got stamped (but not yet tagged). I see now that Jonathan (with RMT hat on, C

PostgreSQL 15 Beta 4 release announcement draft

Hi, I've attached a draft of the PostgreSQL 15 Beta 4 release announcement. Please review for correctness and if there are any omissions. Please provide feedback on the draft no later than Sep 8, 2022 0:00 AoE. Thanks! Jonathan The PostgreSQL Global Development Group announces that the fourt

Re: PostgreSQL 15 Beta 4 release announcement draft

On 9/7/22 4:02 AM, Alvaro Herrera wrote: Hi Jonathan, On 2022-Sep-06, Jonathan S. Katz wrote: * [`MERGE`](https://www.postgresql.org/docs/15/sql-merge.html) statements are explicitly rejected inside of a [common-table expression](https://www.postgresql.org/docs/15/queries-with.html) (aka

Re: PostgreSQL 15 Beta 4 release announcement draft

On 9/7/22 1:18 AM, Erik Rijkers wrote: Op 07-09-2022 om 03:40 schreef Jonathan S. Katz: Hi, I've attached a draft of the PostgreSQL 15 Beta 4 release announcement. Please review for correctness and if there are any omissions. Please provide feedback on the draft no later than Sep 8, 2

Re: PostgreSQL 15 release announcement draft

On 9/1/22 9:10 PM, Jonathan S. Katz wrote: New version attached. Here is a (penultimate?) draft that includes URLs. Please provide any additional feedback no later than 2022-09-14 0:00 AoE. After that, we will begin the translation process. Thanks, Jonathan The PostgreSQL Global

Re: PostgreSQL 15 release announcement draft

On 9/12/22 2:01 PM, Peter Eisentraut wrote: On 12.09.22 18:52, Jonathan S. Katz wrote: On 9/1/22 9:10 PM, Jonathan S. Katz wrote: New version attached. Here is a (penultimate?) draft that includes URLs. Please provide any additional feedback no later than 2022-09-14 0:00 AoE. After that

Re: PostgreSQL 15 release announcement draft

On 9/12/22 3:34 PM, Justin Pryzby wrote: On Mon, Sep 12, 2022 at 12:52:49PM -0400, Jonathan S. Katz wrote: sorted. Using `row_number()`, `rank()`, and `count()` as [window functions](https://www.postgresql.org/docs/15/functions-window.html) also have performance benefits in PostgreSQL 15, and

Re: PostgreSQL 15 release announcement draft

On 9/12/22 4:17 PM, David Rowley wrote: On Tue, 13 Sept 2022 at 04:53, Jonathan S. Katz wrote: Here is a (penultimate?) draft that includes URLs. Please provide any additional feedback no later than 2022-09-14 0:00 AoE. After that, we will begin the translation process. Thanks for drafting

Re: First draft of the PG 15 release notes

On 9/4/22 2:42 PM, Nathan Bossart wrote: I noticed that the v15 release notes still refer to pg_checkpointer, which was renamed to pg_checkpoint in b9eb0ff. diff --git a/doc/src/sgml/release-15.sgml b/doc/src/sgml/release-15.sgml index d432c2db44..362728753a 100644 --- a/doc/src/sgml/release-15.

Re: First draft of the PG 15 release notes

On 9/13/22 7:13 AM, Alvaro Herrera wrote: On 2022-Sep-12, Jonathan S. Katz wrote: + + + Column-level and row-level filtering on + logical replication + publications. + + -column-level filtering +the ability to specify column lists Adjusted to be similar to

PostgreSQL 15 RC1 + GA dates

Hi, The release team is planning to release PostgreSQL 15 Release Candidate 1 (RC1) on 2022-09-29. Please ensure all open items[1] are resolved no later than 2022-09-24 0:00 AoE. Following recent release patterns, we planning for 2022-10-06 to be the GA date. This may change based on what re

Re: why can't a table be part of the same publication as its schema

On 9/19/22 11:16 AM, Alvaro Herrera wrote: diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml index 1ae3287..0ab768d 100644 --- a/doc/src/sgml/logical-replication.sgml +++ b/doc/src/sgml/logical-replication.sgml @@ -1120,6 +1120,11 @@ test_sub=# SELECT *

Re: why can't a table be part of the same publication as its schema

On 9/19/22 4:52 PM, Jonathan S. Katz wrote: On 9/19/22 11:16 AM, Alvaro Herrera wrote: This seems a pretty arbitrary restriction.  It feels like you're adding this restriction precisely so that you don't have to write the code to reject the ALTER .. SET SCHEMA if an incompatible con

Re: why can't a table be part of the same publication as its schema

On 9/20/22 10:55 AM, Mark Dilger wrote: On Sep 19, 2022, at 8:03 PM, Jonathan S. Katz wrote: "When a partitioned table is added to a publication, all of its existing and future partitions are implicitly considered to be part of the publication."[10] Additionally, this is the beh

Re: why can't a table be part of the same publication as its schema

(RMT hat on, unless otherwise noted) On 9/20/22 9:42 AM, Robert Haas wrote: On Mon, Sep 19, 2022 at 11:03 PM Jonathan S. Katz wrote: For #1 (allowing calls that have schema/table overlap...), there appears to be both a patch that allows this (reversing[8]), and a suggestion for dealing with a

Re: why can't a table be part of the same publication as its schema

[personal views, not RMT] On 9/20/22 4:06 PM, Mark Dilger wrote: I don't complain that it is buidling on the existing behavior. I'm *only* concerned about the keywords we're using for this. Consider the following: -- AS ADMIN CREATE USER bob NOSUPERUSER; GRANT ALL PRIVILEGES ON

Re: why can't a table be part of the same publication as its schema

On 9/21/22 10:24 AM, Alvaro Herrera wrote: On 2022-Sep-20, Robert Haas wrote: I don't think we should change this behavior that's already in logical replication. While I understand the reasons why "GRANT ... ALL TABLES IN SCHEMA" has a different behavior (i.e. it's not applied to future objects

Re: why can't a table be part of the same publication as its schema

> On Sep 22, 2022, at 8:02 AM, Alvaro Herrera wrote: > > FWIW I put this to CI: > https://cirrus-ci.com/build/5823276948652032 (master) > > and everything appears to be OK. If anybody has reservations about this > grammar change, please speak up soon, as there's not much time before RC1. >

Re: Assert failure of the cross-check for nullingrels

On 5/12/23 3:02 AM, Richard Guo wrote: On Fri, Mar 17, 2023 at 11:05 AM Richard Guo > wrote: Here is an updated patch with comments and test case.  I also change the code to store 'group_clause_relids' directly in RestrictInfo. BTW, I've added an open i

Re: Assert failure of the cross-check for nullingrels

On 5/16/23 9:49 AM, Tom Lane wrote: "Jonathan S. Katz" writes: Is there a specific commit targeted for v16 that introduced this issue? Does it only affect v16 or does it affect backbranches? It's part of the outer-join-aware-Vars stuff, so it's my fault ... and v16 only

Re: pg_stat_io not tracking smgrwriteback() is confusing

On 5/6/23 1:30 PM, Melanie Plageman wrote: I've done that in the attached v5. [RMT hat] RMT nudge on this thread, as we're approaching the Beta 1 cutoff. From the above discussion, it sounds like it's pretty close to being ready. Thanks, Jonathan OpenPGP_signature Description: OpenPGP d

Re: WL_SOCKET_ACCEPT fairness on Windows

On 3/31/23 11:00 PM, Thomas Munro wrote: I mention this now because I'm not sure whether to consider this an 'open item' for 16, or merely an enhancement for 17. I guess the former, because someone might call that a new denial of service vector. On the other hand, if you fill up the listen que

Re: Order changes in PG16 since ICU introduction

On 5/5/23 8:25 PM, Jeff Davis wrote: On Fri, 2023-04-21 at 20:12 -0400, Robert Haas wrote: On Fri, Apr 21, 2023 at 5:56 PM Jeff Davis wrote: Most of the complaints seem to be complaints about v15 as well, and while those complaints may be a reason to not make ICU the default, they are also an

Re: WL_SOCKET_ACCEPT fairness on Windows

On 5/16/23 4:41 PM, Thomas Munro wrote: On Wed, May 17, 2023 at 2:57 AM Jonathan S. Katz wrote: Given this has sat for a bit, I wanted to see if any of your thinking has changed on whether this should be fixed for v16 or v17. I have personally not formed an opinion yet, but per the current

Re: Possible regression setting GUCs on \connect

On 5/17/23 12:47 PM, Nathan Bossart wrote: On Wed, May 17, 2023 at 08:08:36AM -0400, 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 agre

Re: pg_stat_io not tracking smgrwriteback() is confusing

On 5/17/23 3:19 PM, Andres Freund wrote: Hi, On 2023-05-16 10:30:27 -0400, Jonathan S. Katz wrote: On 5/6/23 1:30 PM, Melanie Plageman wrote: I've done that in the attached v5. [RMT hat] RMT nudge on this thread, as we're approaching the Beta 1 cutoff. From the above discussion,

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 have

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 th

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 b

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

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 saw

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 feedba

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 t

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

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 I

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 t

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 Rowle

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

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: 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 commit/t

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

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 jus

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

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 basi

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

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

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 su

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] https://wiki.postgresql.org/wiki/PostgreSQL_16_Ope

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 (tri

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

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

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 t

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

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

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

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

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

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

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

<    1   2   3   4   5   6   7   >