Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mYeNv-0003K7-Sb for pgsql-performance@arkaria.postgresql.org; Fri, 08 Oct 2021 01:09:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mYeNu-0005FO-OJ for pgsql-performance@arkaria.postgresql.org; Fri, 08 Oct 2021 01:09:14 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mYeNu-0005FE-Fs for pgsql-performance@lists.postgresql.org; Fri, 08 Oct 2021 01:09:14 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mYeNr-0000D1-SX for pgsql-performance@lists.postgresql.org; Fri, 08 Oct 2021 01:09:14 +0000 Received: from bruce by momjian.us with local (Exim 4.92) (envelope-from ) id 1mYeNo-00022e-TW; Thu, 07 Oct 2021 21:09:08 -0400 Date: Thu, 7 Oct 2021 21:09:08 -0400 From: Bruce Momjian To: Laurenz Albe Cc: Jeff Holt , pgsql-performance@lists.postgresql.org Subject: Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle Message-ID: <20211008010908.GA6985@momjian.us> References: <9cecae326e8d73ff9e01c000d738b6a52dc76076.camel@cybertec.at> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9cecae326e8d73ff9e01c000d738b6a52dc76076.camel@cybertec.at> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Oct 4, 2021 at 08:34:29AM +0200, Laurenz Albe wrote: > > Now looking closely at postgreSQL, I see an opportunity to more quickly implement Oracle's current feature list. > > Anything that improves user experience in that respect is welcome, but consider > that each database has different approaches to solve the same problems. > > Before you go to the length of implementing a lot of stuff, check in with > the -hackers list and discuss your ideas. > > Please be a lot more specific than in this e-mail. While it is certainly > fine to sketch your ambitios vision, focus on one specific thing you can > imagine implementing and come up with a design for that. > > Note that "Oracle has it" is not a good enough reason for a PostgreSQL > feature. We think we can do better than they do (at least in many respects). > Also, don't assume that everyone on the -hackers list will be familiar with > certain PostgreSQL features. > > One think that you should keep in mind is that Oracle has to provide different > features in that area because they are not open source. In PostgreSQL, I can > simply read the code or attach a debugger to a backend, and when it comes to > profiling, "perf" works pretty well. So there is less need for these things. > > I don't want to discourage you, but contributing to PostgreSQL can be a lengthy > and tedious process. On the upside, things that make it into core are usually > fairly mature. Jeff, I suggest you consider Laurenz's suggestions above, and try to ignore the comments from Mladen Gogala, since they are caustic and I believe unhelpful. Frankly, we rarely have such caustic comments on the Postgres email lists. I have emailed Mladen Gogala privately to discuss this. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com If only the physical world exists, free will is an illusion.