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 1nlX4N-0008Dt-JQ for pgsql-hackers@arkaria.postgresql.org; Mon, 02 May 2022 14:30:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nlX4L-0008T9-Ac for pgsql-hackers@arkaria.postgresql.org; Mon, 02 May 2022 14:30:33 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nlX4K-0008T0-Pk for pgsql-hackers@lists.postgresql.org; Mon, 02 May 2022 14:30:32 +0000 Received: from mail-ot1-x32a.google.com ([2607:f8b0:4864:20::32a]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nlX4F-0007bK-2a for pgsql-hackers@postgresql.org; Mon, 02 May 2022 14:30:31 +0000 Received: by mail-ot1-x32a.google.com with SMTP id m6-20020a05683023a600b0060612720715so2604145ots.10 for ; Mon, 02 May 2022 07:30:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=fgqZAHc+cLmGf8TQHpQzsehgKzLpCm91oLoGNUykghM=; b=jsm6Xe9PvE7as1l4kaeVfPd2g8/rG0xzjReHzZTp4vkyBcV+uDyL64PcR5tJDT3vvo 5LjUV0xL2myIuauFirMoxgs3LxJVuOMC9mNGkSW3c6VkWKttl7KU9UCy4OodPjZ+IaO2 OS7J8b3h05gXKLDvZ+ibTmYzzxinYHjEHu0EiMQk8N6SGgCJM9u9QKkBdhY0eqL9WwXH BXIXgY1vIaN6FAlhQhEjYiOapC2KW6qZFxlFcl8ivL/0m1Rg2iGlwPeEH/Ib2BmY9E8E EM7NgNPvEuJOxQygTvjKHN8kQJvLy6WSI2X0ptuJy8wbYsiU5YafexmAmeUJUBZrTlgB bqMA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=fgqZAHc+cLmGf8TQHpQzsehgKzLpCm91oLoGNUykghM=; b=kNZSVlQY8P+KMMojshK7asCbRRQF3seoITmAEBWPYjTCgsyh7aY2wflU9iCplTs/gD kd8fQzTsDdaZflfHstJwXvwWo+X74ZUolgHaFmvroVx+gApiXRnTEBDc//c7YvZnaeCE ogml7s4qAOSfyDZeUY8Uco74Hff8WNZL+0YcJL9CaBo5O/9z/p+zqcOBkyj9rr/tuMwQ ZDR0Et9bcj0rG/X5DAMz6l4CyLq+DSbOLBTm0CDNohwFLW+6jthifHfvdKxiJ+SsueCi NYS6RRAif35Rxn4aX74AjDwCm9OqcHQynp/cG/8Zoiey5HSPc2RI2Syj1g8ZbO7BWx6p VGZA== X-Gm-Message-State: AOAM530HJyAky0dSCvuxN7FD8RrEO2BKwruUy8mTp6dNlhXdmBu5l/Ce V8uwBwCm4HmJ62kDd6Bpt8Aa4G8dBIg= X-Google-Smtp-Source: ABdhPJyE/TCa+TFcDxIt5XDsActNlI+DO5BpfRDB7tSZX1j4YDiyBWIlHG0nFHVhCXwHGz4Epfx0yw== X-Received: by 2002:a9d:152:0:b0:606:1e84:ad56 with SMTP id 76-20020a9d0152000000b006061e84ad56mr1454034otu.80.1651501826374; Mon, 02 May 2022 07:30:26 -0700 (PDT) Received: from moubin ([4.53.40.195]) by smtp.gmail.com with ESMTPSA id w23-20020a9d6757000000b0060603221257sm2905997otm.39.2022.05.02.07.30.25 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 02 May 2022 07:30:25 -0700 (PDT) Date: Mon, 2 May 2022 07:30:23 -0700 From: Mark Wong To: Peter Geoghegan Cc: Mahesh Gouru , PostgreSQL Hackers Subject: Re: DBT-5 Stored Procedure Development (2022) Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, May 02, 2022 at 07:14:28AM -0700, Mark Wong wrote: > On Tue, Apr 26, 2022, 10:45 AM Peter Geoghegan wrote: > > > On Tue, Apr 26, 2022 at 10:36 AM Mark Wong wrote: > > > I'm afraid not. I'm guessing that pulling in egen 1.14 would address > > > that. Maybe it would make sense to put that on the top of todo list if > > > this project is accepted... > > > > Wouldn't it be a prerequisite here? I don't actually have any reason > > to prefer the old function-based code to the new stored procedure > > based code. Really, all I'm looking for is a credible implementation > > of TPC-E that I can use to model some aspects of OLTP performance for > > my own purposes. > > > > TPC-C (which I have plenty of experience with) has only two secondary > > indexes (in typical configurations), and doesn't really stress > > concurrency control at all. Plus there are no low cardinality indexes > > in TPC-C, while TPC-E has quite a few. Chances are high that I'd learn > > something from TPC-E, which has all of these things -- I'm really > > looking for bottlenecks, where Postgres does entirely the wrong thing. > > It's especially interesting to me as somebody that focuses on B-Tree > > indexing. I think it could be done in either order. While it's not ideal that the kit seems to work most reliably as-is on RHEL/Centos/etc. 6, I think that could provide some confidence in getting familiar with something on a working platform. The updates to the stored functions/procedures would be the same regardless of egen version. If we get the project slot, we can talk further about what to actually tackle first. Regards, Mark