Re: minimum Meson version

Hi On 6/18/25 1:07 PM, Robert Haas wrote: Since any policy that anyone is likely to actually propose falls somewhere between those two extremes, half of us are then bitterly unhappy with it. Which is why I tried to add Devrim to the thread. What builds on yum.postgresql.org are using meson ?

Re: minimum Meson version

Hi, On 6/17/25 2:23 PM, Andres Freund wrote: After all full support for RHEL 8 has ended a year ago. Yes, full support ended May 31, 2024 - but extended support ends May 31, 2029. Devrim, feedback ? Best regards, Jesper

Re: Improve CRC32C performance on SSE4.2

Hi Nathan, On 6/14/25 9:56 AM, Nathan Bossart wrote: I'm also genuinely curious why folks are using -O0... Personally, I use -O0 -fno-omit-frame-pointer for FlameGraph [1] investigations. [1] https://github.com/brendangregg/FlameGraph Best regards, Jesper

Re: pg_rewind: Doc update for PostgreSQL 18

Hi Nathan, On 6/9/25 3:15 PM, Nathan Bossart wrote: + the cluster was initialized with initdb. Data checksums + are enabled by default starting from PostgreSQL 18. must also be set to on, but is enabled by default. +1 for fixing this, but I'd like to bikeshed on the wording a bit.

pg_rewind: Doc update for PostgreSQL 18

Hi, Attached is a documentation update for pg_rewind since data checksums are enabled by default starting from PostgreSQL 18. Feedback welcome ! Best regards, Jesper diff --git a/doc/src/sgml/ref/pg_rewind.sgml b/doc/src/sgml/ref/pg_rewind.sgml index 5485033ed8c..b305d788a6e 100644 --- a/doc

Re: GSoC 2025 - Looking for Beginner-Friendly PostgreSQL Project

Hi, On 3/26/25 2:14 PM, Kruti Popat wrote: My name is Kruti Popat, and I am an IT engineering student interested in contributing to PostgreSQL for GSoC 2025. You can see the GSoC 2025 projects here: https://wiki.postgresql.org/wiki/GSoC_2025 and reach out to the mentors. Thanks ! Best r

Re: Inquiry About Google Summer of Code Projects

Hi Mohamed, On 2/5/25 10:29 AM, Mohamed Badawy wrote: I hope this message finds you well. My name is Mohamed, and I am currently a third-year Computer Engineering student. I possess skills in C++, C#, Python, Object-Oriented Programming (OOP), Data Structures and Algorithms (DSA), SQL, and SQ

Re: protocol-level wait-for-LSN

Hi, On 10/30/24 3:49 PM, Jelte Fennema-Nio wrote: On Wed, 30 Oct 2024 at 19:04, Jesper Pedersen wrote: Having LSN would be nice, but to break all existing implementations, no. Having to specify with startup parameters how a core message format looks like sounds like a bad idea to me, It

Re: protocol-level wait-for-LSN

Hi, On 10/30/24 1:45 PM, Jelte Fennema-Nio wrote: On Wed, 30 Oct 2024 at 18:18, Ants Aasma wrote: The idea is great, I have been wanting something like this for a long time. For future proofing it might be a good idea to not require the communicated-waited value to be a LSN. Yours and Matthi

Re: protocol-level wait-for-LSN

Hi, On 10/29/24 12:03 PM, Jesper Pedersen wrote: On 10/28/24 12:58 PM, Heikki Linnakangas wrote: I'd suggest adding a new message type for this, so that it works the same with simple and extended query. Or if you just want to wait without issuing any query. I agree it is a good idea to

Re: protocol-level wait-for-LSN

Hi Peter, On 10/28/24 12:58 PM, Heikki Linnakangas wrote: I'd suggest adding a new message type for this, so that it works the same with simple and extended query. Or if you just want to wait without issuing any query. I agree it is a good idea to have a feature like this. However, I agree w

Re: sunsetting md5 password support

On 10/10/24 5:45 PM, Heikki Linnakangas wrote: On 11/10/2024 00:03, Bruce Momjian wrote: On Wed, Oct  9, 2024 at 10:30:15PM +0200, Jelte Fennema-Nio wrote: On Wed, 9 Oct 2024 at 21:55, Nathan Bossart wrote: In this message, I propose a multi-year, incremental approach to remove MD5 password

Re: commitfest.postgresql.org is no longer fit for purpose

Hi, On 5/16/24 4:31 PM, Joe Conway wrote: Yeah.  I think that Robert put his finger on a big part of the problem, which is that punting a patch to the next CF is a lot easier than rejecting it, particularly for less-senior CFMs who may not feel they have the authority to say no (or at least doub

Re: New committers: Melanie Plageman, Richard Guo

On 4/26/24 07:54, Jonathan S. Katz wrote: 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! Congrats ! Best regar

Re: PostgreSQL 17 Release Management Team & Feature Freeze

Hi, On 4/8/24 14:15, Tomas Vondra wrote: I think we need to fix & improve that - not to rework/push it at the very end. This is going to be very extreme... Either a patch is ready for merge or it isn't - when 2 or more Committers agree on it then it can be merged - the policy have to be di

Re: 2023-11-09 release announcement draft

Hi, On 11/6/23 17:04, Jonathan S. Katz wrote: 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). s/PostgreS

Re: Commitfest manager for September

Hi Melanie, On 8/28/23 11:42, Melanie Plageman wrote: I too had planned to volunteer to help. I volunteer to do a triage/summary of patch statuses, as has been done occasionally in the past [1]. Have folks found this helpful in the past? Having a summary to begin with is very helpful for revi

Re: New committers: Nathan Bossart, Amit Langote, Masahiko Sawada

On 4/20/23 13:40, Tom Lane wrote: The Core Team would like to extend our congratulations to Nathan Bossart, Amit Langote, and Masahiko Sawada, who have accepted invitations to become our newest Postgres committers. Please join me in wishing them much success and few reverts. Huge congrats !

Re: GSOC2023

Hi, On 12/28/22 21:10, diaa wrote: *Hi Sir.* I’m Computer engineering student from Egypt Interested in Database Management Systems. Can I know details about the list of ideas for 2023 projects or how to prepare myself to be ready with the required knowledge? Thanks for your interest in GSoC 2

Re: GSoC: pgagroal: SCRAM-SHA-256-PLUS support (2022)

Hi, On 4/18/22 04:16, wanghaitao0...@zju.edu.cn wrote: I'm Haitao Wang, interested in participating in GSOC 2022 PostgreSQL projects. Attached is my proposal. Please check! Thanks for your proposal to Google Summer of Code 2022 ! We'll follow up off-list to get this finalized. Best regards

Re: GsoC: pgexporter: Custom file

Hi, On 4/17/22 04:43, dl x wrote: My name is Donglin Xie, a MSc. student at Zhejiang University, in China. I am interested in the project *pgexporter: Custom_file.* The proposal is attached to this email. Looking forward to the suggestions! Thanks for your proposal to Google Summer of Code

Re: GSoC: pgmoneta: Write-Ahead Log (WAL) infrastructure (2022)

Hi, On 4/16/22 13:06, dl x wrote: My name is Donglin Xie, a MSc. student at Zhejiang University, in China. I am interested in the project *pgmoneta: Write-Ahead Log (WAL) infrastructure.* The proposal is attached to this email. Looking forward to the suggestions! Thanks for your proposal to

Re: GSoC 2022: Proposal of pgmoneta on-disk encryption

Hi Jichen, On 4/13/22 10:40, Solo Kyo wrote: To whom it may concern: Hi, I am Jichen Xu. I am a first year master computer science student at Waseda University. Here is a link to my proposal: https://docs.google.com/document/d/1vdgPY5wvhjhrX9aSUw5mTDOnXwEQNcr4cxfzuSHMWlg Looking forward to work

Re: GSoC: pgmoneta, storage API

Hi Mariam, On 4/4/22 09:16, Mariam Fahmy wrote: Hope you’re having a good day! I am Mariam Fahmy, A senior computer and systems engineering student at faculty of engineering, AinShams university. I am interested in working with pgmoneta during GSoC 2022. Here is a link to the draft proposal fo

Re: GSoC: pgmoneta: Write-Ahead Log (WAL) infrastructure (2022)

Hi Jinlang, On 4/1/22 12:39, Jinlang Wang wrote: To whom it may concern: Here is my proposal (https://docs.google.com/document/d/1KKKDU6iP0GOkAMSdGRyxFJRgW964JFVROnpKkbzWyNw/edit?usp=sharing )

Re: Index Skip Scan (new UniqueKeys)

On 6/9/20 06:22, Dmitry Dolgov wrote: Here is a new version of index skip scan patch, based on v8 patch for UniqueKeys implementation from [1]. I want to start a new thread to simplify navigation, hopefully I didn't forget anyone who actively participated in the discussion. This CommitFest ent

Re: MDAM techniques and Index Skip Scan patch

On 3/23/22 18:22, Dmitry Dolgov wrote: The CF item could be set to RwF, what would you say, Jesper? We want to thank the community for the feedback that we have received over the years for this feature. Hopefully a future implementation can use Tom's suggestions to get closer to a committab

Re: Portability report: ninja

Hi, On 11/1/21 15:25, Tom Lane wrote: So it's pretty clear that if we go this way, it'll be the end of the line for support for some very old OS versions. I can't, however, argue with the idea that it's reasonable to require POSIX 2001 support now. Based on these results, I doubt that ninja wi

Re: MDAM techniques and Index Skip Scan patch

Hi Peter, On 10/21/21 22:16, Peter Geoghegan wrote: I returned to the 1995 paper "Efficient Search of Multidimensional B-Trees" [1] as part of the process of reviewing v39 of the skip scan patch, which was posted back in May. It's a great paper, and anybody involved in the skip scan effort shoul

Re: Triage on old commitfest entries

On 10/3/21 16:18, Peter Geoghegan wrote: Index Skip Scan 16 Last substantive discussion 2021-05, currently passing cfbot Seems possibly useful, but we're not making progress. This feature is definitely useful. My pet theory is that it hasn't made more progress because it requi

Re: Triage on old commitfest entries

Hi, On 10/3/21 16:18, Peter Geoghegan wrote: Index Skip Scan 16 Last substantive discussion 2021-05, currently passing cfbot Seems possibly useful, but we're not making progress. This feature is definitely useful. My pet theory is that it hasn't made more progress because it

Increase log level in xlogreader.c ?

Hi, I have a 13.4 based setup (physical streaming replication) where the replica does the attach log upon startup, and when the first message is sent from the primary. There is the FATAL from when the WAL receiver shuts down, but I think it would be a benefit to have report_invalid_record()

Re: Middleware Messages for FE/BE

Hi Simon, On 8/20/21 10:39 AM, Simon Riggs wrote: Yeah, but it is a change to the protocol which means that the client drivers and middleware ecosystem needs to be updated to support that message. No, because FE messages don't need to be handled by the client, they just send them. Yes, but t

Re: Middleware Messages for FE/BE

Hi Hannu, On 8/19/21 3:52 PM, Hannu Krosing wrote: Jesper, please don't confuse my ramblings with Simon's initial proposal. As I understand, the original proposal was just about adding a new wire protocol message type, which then could be used for emitting custom messages by middleware support

Re: Middleware Messages for FE/BE

Hi, On 8/19/21 1:13 PM, Simon Riggs wrote: We need to be able to send the middleware a message. Replies can be sent as NoticeResponse, if needed, which already exists. Yeah, but you need the client driver - of all languages - to understand that notice. And, if different middleware uses diffe

Re: Middleware Messages for FE/BE

Hi Simon, On 8/19/21 4:33 AM, Simon Riggs wrote: The current FE/BE protocol assumes that the client is talking to the server directly. If middleware wants to do something like load balancing, the only current option is to inspect the incoming commands and take action from that. That approach per

Re: New committers: Daniel Gustafsson and John Naylor

On 6/30/21 4:43 PM, Tom Lane wrote: The Core Team would like to extend our congratulations to Daniel Gustafsson and John Naylor, who have accepted invitations to become our newest Postgres committers. Please join me in wishing them much success and few bugs. regards, tom

Re: [GSoC] Metrics and Monitoring for pgagroal

Hi Junduo, On 4/9/21 11:53 AM, Junduo Dong wrote: I'm Junduo Dong, a 22-year-old studying at China University of Geosciences. I would like to participate in the project "pgagroal: Metrics and monitoring" on page "https://wiki.postgresql.org/wiki/GSoC_2021"; for GSoC 2021. Attachment is the pro

Re: [PATCH] Keeps tracking the uniqueness with UniqueKey

Hi, On 12/5/20 10:38 PM, Andy Fan wrote: Currently the UniqueKey is defined as a List of Expr, rather than EquivalenceClasses. A complete discussion until now can be found at [1] (The messages I replied to also care a lot and the information is completed). This patch has stopped at this place fo

Re: [PATCH] Keeps tracking the uniqueness with UniqueKey

Hi, On 11/30/20 5:04 AM, Heikki Linnakangas wrote: On 26/11/2020 16:58, Andy Fan wrote: This patch has stopped moving for a while,  any suggestion about how to move on is appreciated. The question on whether UniqueKey.exprs should be a list of EquivalenceClasses or PathKeys is unresolved. I

Re: Index Skip Scan

Hi Peter, Thanks for your feedback; Dmitry has followed-up with some additional questions. On 1/20/20 8:05 PM, Peter Geoghegan wrote: This is definitely not okay. I suggest that you find a way to add assertions to code like _bt_readpage() that verify that we do in fact have the buffer conte

Re: Index Skip Scan

find the updated patches attached that Dmitry and I made. Thanks again ! Best regards, Jesper >From 3c540c93307e6cbe792b31b12d4ecb025cd6b327 Mon Sep 17 00:00:00 2001 From: jesperpedersen Date: Fri, 15 Nov 2019 09:46:05 -0500 Subject: [PATCH 1/2] Unique key Design by David Rowley. Author: Jesper Pedersen --- src/backe

Re: Index Skip Scan

Hi, On 11/11/19 1:24 PM, Jesper Pedersen wrote: v29 using UniqueKey attached. Just a small update to the UniqueKey patch to hopefully keep CFbot happy. Feedback, especially on the planner changes, would be greatly appreciated. Best regards,  Jesper >F

Re: Index Skip Scan

for your patch ! v29 using UniqueKey attached. Best regards, Jesper >From 4e27a04702002d06f60468f8a9033d2ac2e12d8a Mon Sep 17 00:00:00 2001 From: jesperpedersen Date: Mon, 11 Nov 2019 08:49:43 -0500 Subject: [PATCH 1/2] Unique key Design by David Rowley. Author: Jesper Pedersen --- src

Re: Application name for pg_basebackup and friends

On 11/7/19 1:51 AM, Michael Paquier wrote: I don't think we need a new comand line switch for it. +1. Please note that I have marked this patch as rejected in the CF app, per the arguments upthread. Ok, agreed. Thanks for the feedback ! Best regards, Jesper

Application name for pg_basebackup and friends

dd an -a / --appname command line switch to control the application_name property. Author: Jesper Pedersen --- doc/src/sgml/ref/pg_basebackup.sgml| 11 +++ doc/src/sgml/ref/pg_receivewal.sgml| 11 +++ doc/src/sgml/ref/pg_recvlogical.sgml | 11 +++ src/bin/pg_ba

Re: Index Skip Scan

Author: Jesper Pedersen --- src/backend/nodes/outfuncs.c | 14 +++ src/backend/nodes/print.c | 39 +++ src/backend/optimizer/path/Makefile| 2 +- src/backend/optimizer/path/allpaths.c | 8 ++ src/backend/optimizer/path/costsize.c | 5 + src/backend/optimi

Re: pg_receivewal documentation

Hi, On 7/23/19 10:29 PM, Michael Paquier wrote: Thanks. Applied down to 9.6 where remote_apply has been introduced, with tweaks for 9.6 as the tool is named pg_receivexlog there. Thanks to everybody involved ! Best regards, Jesper

Re: pg_receivewal documentation

Author: Robert Haas Review-by: Michael Paquier, Álvaro Herrera, Laurenz Albe and Jesper Pedersen --- doc/src/sgml/ref/pg_receivewal.sgml | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/doc/src/sgml/ref/pg_receivewal.sgml b/doc/src/sgml/ref/pg_receivewal.sgml index 05

Re: pg_receivewal documentation

rera, Laurenz Albe and Jesper Pedersen --- doc/src/sgml/ref/pg_receivewal.sgml | 21 ++--- 1 file changed, 10 insertions(+), 11 deletions(-) diff --git a/doc/src/sgml/ref/pg_receivewal.sgml b/doc/src/sgml/ref/pg_receivewal.sgml index e96d753955..beab6f0391 100644 --- a/doc

Re: Index Skip Scan

Hi, On 7/22/19 1:44 AM, David Rowley wrote: Here are the comments I noted down during the review: cost_index: I know you've not finished here, but I think it'll need to adjust tuples_fetched somehow to account for estimate_num_groups() on the Path's unique keys. Any Eclass with an ec_has_const

Re: pg_receivewal documentation

Hi, On 7/18/19 9:09 PM, Michael Paquier wrote: pg_receivewal -D /tmp/wal -S replica1 --synchronous -h localhost -p 5432 -U repluser -W psql -c 'SELECT * FROM pg_stat_replication;' postgres psql -c 'SELECT * FROM pg_replication_slots;' postgres psql -c 'CREATE DATABASE test' postgres In what sce

Re: pg_receivewal documentation

Hi, On 7/18/19 9:27 PM, Michael Paquier wrote: The location of the warning is also harder to catch for the reader, so instead let's move it to the top where we have an extra description for --synchronous. I am finishing with the attached that I would be fine to commit and back-patch as needed.

Re: pg_receivewal documentation

n't apply WAL, and as such synchronous-commit needs to be remote_write or lower. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Authors: Michael Paquier, Álvaro Herrera, Laurenz Albe and Jesper Pedersen Review-by: Michael Paquier, Álvaro Herrera

Re: pg_receivewal documentation

Hi Laurenz, On 7/17/19 5:21 PM, Laurenz Albe wrote: That's factually wrong. "on" (wait for WAL flush) works fine with pg_receivewal, only "remote_apply" doesn't. Please, try mkdir /tmp/wal initdb /tmp/pgsql pg_ctl -D /tmp/pgsql -l /tmp/logfile start psql postgres SELECT pg_create_physical_r

Re: pg_receivewal documentation

ransfer-Encoding: 8bit Authors: Álvaro Herrera, Laurenz Albe and Jesper Pedersen Review-by: Álvaro Herrera, Laurenz Albe and Jesper Pedersen --- doc/src/sgml/ref/pg_receivewal.sgml | 13 + 1 file changed, 13 insertions(+) diff --git a/doc/src/sgml/ref/pg_receivewal.sgml b/doc/

Re: pg_receivewal documentation

CH] Highlight that pg_receivewal doesn't apply WAL, and as such synchronous-commit needs to be remote_write or lower. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Authors: Álvaro Herrera, Laurenz Albe and Jesper Pedersen Review-by: Álvaro Herrera,

Re: Index Skip Scan

Hi David, On 7/11/19 7:38 AM, David Rowley wrote: The UniqueKeys idea is quite separate from pathkeys. Currently, a Path can have a List of PathKeys which define the order that the tuples will be read from the Plan node that's created from that Path. The idea with UniqueKeys is that a Path can

Re: Index Skip Scan

Hi David, On 7/11/19 7:38 AM, David Rowley wrote: The UniqueKeys idea is quite separate from pathkeys. Currently, a Path can have a List of PathKeys which define the order that the tuples will be read from the Plan node that's created from that Path. The idea with UniqueKeys is that a Path can

Re: pg_receivewal documentation

write or lower. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Authors: Álvaro Herrera, Laurenz Albe and Jesper Pedersen Review-by: Álvaro Herrera, Laurenz Albe and Jesper Pedersen --- doc/src/sgml/ref/pg_receivewal.sgml | 8 1 file ch

Re: Index Skip Scan

Hi, On 7/9/19 10:14 PM, Thomas Munro wrote: Thomas, do you have any ideas for this ? I can see that MySQL did the functionality in two change sets (base and function support), but like you said we shouldn't paint ourselves into a corner. I think amskip() could be augmented by later patches to

Re: pg_receivewal documentation

Hi, On 7/10/19 4:04 AM, Michael Paquier wrote: On Wed, Jul 10, 2019 at 12:22:02AM +0200, Laurenz Albe wrote: Works for me. Marked as "ready for committer". Hmm. synchronous_commit is user-settable, which means that it is possible to enforce a value in the connection string doing the connect

Re: pg_receivewal documentation

Hi, On 7/9/19 6:22 PM, Laurenz Albe wrote: Works for me. Marked as "ready for committer". Thank you ! Best regards, Jesper

Re: pg_receivewal documentation

Hi Laurenz, On 7/9/19 5:16 AM, Laurenz Albe wrote: On Thu, 2019-06-27 at 10:06 -0400, Jesper Pedersen wrote: Here is a patch for the pg_receivewal documentation to highlight that WAL isn't acknowledged to be applied. I think it is a good idea to document this, but I have a few quibbles

Re: Index Skip Scan

Hi, On 7/4/19 6:59 AM, Thomas Munro wrote: For the MIN query you just need a path with Pathkeys: { i ASC, j ASC }, UniqueKeys: { i, j }, doing the MAX query you just need j DESC. David, are you thinking about something like the attached ? Some questions. * Do you see UniqueKey as a "comple

Re: Index Skip Scan

Hi Thomas and David, Thanks for the feedback ! On 7/2/19 8:27 AM, David Rowley wrote: On Tue, 2 Jul 2019 at 21:00, Thomas Munro wrote: I took this for a quick spin today. The DISTINCT ON support is nice and I think it will be very useful. I've signed up to review it and will have more to sa

Re: POC: converting Lists into arrays

Hi, On 7/1/19 2:44 PM, Tom Lane wrote: Yup, here's a rebase against HEAD (and I also find that check-world shows no problems). Thanks - no further comments. This is pretty much of a pain to maintain, since it changes the API for lnext() which is, um, a bit invasive. I'd like to make a deci

Re: POC: converting Lists into arrays

Hi, On 5/25/19 11:48 AM, Tom Lane wrote: The cfbot noticed a set-but-not-used variable that my compiler hadn't whined about. Here's a v5 to pacify it. No other changes. This needs a rebase. After that check-world passes w/ and w/o -DDEBUG_LIST_MEMORY_USAGE. There is some unneeded MemoryC

pg_receivewal documentation

2019 09:54:44 -0400 Subject: [PATCH] Highlight that pg_receivewal doesn't acknowledge that WAL has been applied, and as such synchronous-commit needs to be remote_write or lower. Author: Jesper Pedersen --- doc/src/sgml/ref/pg_receivewal.sgml | 8 1 file changed, 8 insertions(+) di

Re: Index Skip Scan

d improved by Dmitry Dolgov and Jesper Pedersen. [1] https://wiki.postgresql.org/wiki/Loose_indexscan [2] https://www.postgresql.org/message-id/flat/CADLWmXXbTSBxP-MzJuPAYSsL_2f0iPm5VWPbCvDbVvfX93FKkw%40mail.gmail.com --- contrib/bloom/blutils.c | 1 + doc/src/sgm

Re: Index Skip Scan

Hi David, On 6/14/19 3:19 AM, David Rowley wrote: I read over this thread a few weeks ago while travelling back from PGCon. (I wish I'd read it on the outward trip instead since it would have been good to talk about it in person.) First off. I think this is a pretty great feature. It certainly

Re: Index Skip Scan

Hi James, On 6/13/19 11:40 PM, James Coleman wrote: I've previously noted upthread (along with several others), that I don't see a good reason to limit this new capability to index only scans. In addition to the reasons upthread, this also prevents using the new feature on physical replicas sinc

Re: Index Skip Scan

y Thomas Munro [2], revived and improved by Dmitry Dolgov and Jesper Pedersen. [1] https://wiki.postgresql.org/wiki/Loose_indexscan [2] https://www.postgresql.org/message-id/flat/CADLWmXXbTSBxP-MzJuPAYSsL_2f0iPm5VWPbCvDbVvfX93FKkw%40mail.gmail.com --- contrib/bloom/blutils.c

Re: Index Skip Scan

Hi Rafia, On 6/1/19 6:03 AM, Rafia Sabih wrote: Here is my repeatable test case, create table t (market text, feedcode text, updated_at timestamptz, value float8) ; create index on t (market, feedcode, updated_at desc); insert into t values('TEST', 'abcdef', (select timestamp '2019-01-10 20:00:

Re: Index Skip Scan

Hi Floris, On 6/1/19 12:10 AM, Floris Van Nee wrote: Given a table definition of (market text, feedcode text, updated_at timestamptz, value float8) and an index on (market, feedcode, updated_at desc) (note that this table slightly deviates from what I described in my previous mail) and fillin

Re: New committer: David Rowley

On 5/30/19 11:39 AM, Magnus Hagander wrote: Congratulations to David, may the buildfarm be gentle to him, and his first revert far away! Congrats ! Best regards, Jesper

Re: COLLATE: Hash partition vs UPDATE

Hi Amit, On 4/8/19 11:18 PM, Amit Langote wrote: As of this commit, hashing functions hashtext() and hashtextextended() require a valid collation to be passed in. ISTM, satisfies_hash_partition() that's called by hash partition constraint checking should have been changed to use FunctionCall2Co

COLLATE: Hash partition vs UPDATE

Hi, The following case -- test.sql -- CREATE TABLE test (a text PRIMARY KEY, b text) PARTITION BY HASH (a); CREATE TABLE test_p0 PARTITION OF test FOR VALUES WITH (MODULUS 2, REMAINDER 0); CREATE TABLE test_p1 PARTITION OF test FOR VALUES WITH (MODULUS 2, REMAINDER 1); -- CREATE INDEX idx_tes

Re: partitioned tables referenced by FKs

On 4/3/19 1:52 PM, Alvaro Herrera wrote: Pushed, many thanks Amit and Jesper for reviewing. Thank you for working on this feature. Best regards, Jesper

Re: partitioned tables referenced by FKs

Hi, On 4/1/19 4:03 PM, Alvaro Herrera wrote: I'm satisfied with this patch now, so I intend to push early tomorrow. Passes check-world, and my tests. Best regards, Jesper

Re: partitioned tables referenced by FKs

Hi Alvaro, On 3/28/19 2:59 PM, Alvaro Herrera wrote: I ended up revising the dependencies that we give to the constraint in the partition -- instead of giving it partition-type dependencies, we give it an INTERNAL dependency. Now when you request to drop the partition, it says this: create tab

Re: partitioned tables referenced by FKs

Hi, On 3/29/19 12:29 PM, Alvaro Herrera wrote: On 2019-Mar-29, Jesper Pedersen wrote: Maybe the "(" / ")" in the CASCADE description should be removed from ref/drop_table.sgml as part of this patch. I'm not sure what text you propose to remove? Just the attached.

Re: partitioned tables referenced by FKs

Hi, On 3/29/19 11:22 AM, Alvaro Herrera wrote: On 2019-Mar-29, Jesper Pedersen wrote: Could expand a bit on the change to DEPENDENCY_INTERNAL instead of DEPENDENCY_PARTITION_PRI / DEPENDENCY_PARTITION_SEC ? The PARTITION dependencies work in a way that doesn't do what we want. Admit

Re: partitioned tables referenced by FKs

Hi Alvaro, On 3/28/19 2:59 PM, Alvaro Herrera wrote: I ended up revising the dependencies that we give to the constraint in the partition -- instead of giving it partition-type dependencies, we give it an INTERNAL dependency. Now when you request to drop the partition, it says this: create tab

Re: partitioned tables referenced by FKs

Hi, On 3/26/19 5:39 PM, Alvaro Herrera wrote: As I said before, I'm thinking of getting rid of the whole business of checking partitions on the referenced side of an FK at DROP time, and instead jut forbid the DROP completely if any FKs reference an ancestor of that partition. Will that allow

Re: partitioned tables referenced by FKs

Hi Amit, On 3/26/19 2:06 AM, Amit Langote wrote: Wouldn't you get the same numbers on HEAD too? IOW, I'm not sure how the patch here, which seems mostly about getting DDL in order to support foreign keys on partitioned tables, would have affected the result of this benchmark. Can you clarify y

Re: partitioned tables referenced by FKs

Hi Alvaro, On 3/21/19 6:18 PM, Alvaro Herrera wrote: On 2019-Mar-21, Jesper Pedersen wrote: pgbench -M prepared -f select.sql I'm seeing 82.64% spent in GetCachedPlan(). plan_cache_mode is auto. Hmm, I can't reproduce this at all ... I don't even see GetCachedPlan in t

Re: partitioned tables referenced by FKs

Hi Alvaro, On 3/21/19 4:49 PM, Alvaro Herrera wrote: I think the attached is a better solution, which I'll go push shortly. I see you pushed this, plus 0002 as well. Thanks ! Best regards, Jesper

Re: speeding up planning with partitions

Hi Amit, On 3/22/19 3:39 AM, Amit Langote wrote: I took a stab at this. I think rearranging the code in make_partitionedrel_pruneinfo() slightly will take care of this. The problem is that make_partitionedrel_pruneinfo() does some work which involves allocating arrays containing nparts element

Re: partitioned tables referenced by FKs

Hi Alvaro, On 3/18/19 6:02 PM, Alvaro Herrera wrote: I spent a few hours studying this and my conclusion is the opposite of yours: we should make addFkRecurseReferencing the recursive one, and CloneFkReferencing a non-recursive caller of that. So we end up with both addFkRecurseReferenced and a

Re: speeding up planning with partitions

Hi Amit, On 3/19/19 8:41 PM, Amit Langote wrote: I have fixed all. Attached updated patches. The comments in the thread has been addressed, so I have put the CF entry into Ready for Committer. Best regards, Jesper

Re: speeding up planning with partitions

Hi, On 3/19/19 11:15 PM, Imai, Yoshikazu wrote: Here the details. [creating partitioned tables (with 1024 partitions)] drop table if exists rt; create table rt (a int, b int, c int) partition by range (a); \o /dev/null select 'create table rt' || x::text || ' partition of rt for values from ('

Re: pg_upgrade: Pass -j down to vacuumdb

2aa3ed51aff3cbe75c Mon Sep 17 00:00:00 2001 From: jesperpedersen Date: Tue, 12 Mar 2019 16:02:27 -0400 Subject: [PATCH] Highlight that the --jobs option isn't passed down to vacuumdb. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Author: Jesper Pe

Re: speeding up planning with partitions

Hi Amit, On 3/12/19 4:22 AM, Amit Langote wrote: I wrestled with this idea a bit and concluded that we don't have to postpone *all* of preprocess_targetlist() processing to query_planner, only the part that adds row mark "junk" Vars, because only those matter for the problem being solved. To re

Re: speeding up planning with partitions

Hi, On 3/5/19 5:24 AM, Amit Langote wrote: Attached an updated version. Need a rebase due to 898e5e3290. Best regards, Jesper

Re: speeding up planning with partitions

On 3/5/19 5:24 AM, Amit Langote wrote: Attached an updated version. This incorporates fixes for both Jesper's and Imai-san's review. I haven't been able to pin down the bug (or whatever) that makes throughput go down as the partition count increases, when tested with a --enable-cassert build.

Re: speeding up planning with partitions

Hi Amit, Passes check-world. On 3/4/19 5:38 AM, Amit Langote wrote: See patch 0001. +* members of any appendrels we find here are added built later when s/built// See patch 0002. + grouping_planner(root, false, 0.0 /* retrieve all tuples */); Move comment out of function

Re: partitioned tables referenced by FKs

Hi Alvaro, On 2/28/19 1:28 PM, Alvaro Herrera wrote: Rebased to current master. I'll reply later to handle the other issues you point out. Applying with hunks. With 0003 using export CFLAGS="-DCOPY_PARSE_PLAN_TREES -O0 -fno-omit-frame-pointer" && CC="ccache gcc" ./configure --prefix /usr/

Re: Index Skip Scan

Hi, On 1/31/19 1:31 AM, Kyotaro HORIGUCHI wrote: At Wed, 30 Jan 2019 18:19:05 +0100, Dmitry Dolgov <9erthali...@gmail.com> wrote in A bit of adjustment after nodes/relation -> nodes/pathnodes. I had a look on this. The name "index skip scan" is a different feature from the feature with the

Re: pg_upgrade: Pass -j down to vacuumdb

71a26a2ba150c1067ee21bb242 Mon Sep 17 00:00:00 2001 From: jesperpedersen Date: Fri, 21 Dec 2018 05:05:31 -0500 Subject: [PATCH] Highlight that the --jobs option isn't passed down to vacuumdb by default. Author: Jesper Pedersen --- doc/src/sgml/ref/pgupgrade.sgml |

  1   2   3   >