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 1o71Ba-0001jq-So for pgsql-hackers@arkaria.postgresql.org; Thu, 30 Jun 2022 20:54:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1o71BZ-0001Qz-2P for pgsql-hackers@arkaria.postgresql.org; Thu, 30 Jun 2022 20:54:49 +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 1o71BY-0001Qc-Nd for pgsql-hackers@lists.postgresql.org; Thu, 30 Jun 2022 20:54:48 +0000 Received: from mail-pj1-x102c.google.com ([2607:f8b0:4864:20::102c]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1o71BS-0004os-31 for pgsql-hackers@lists.postgresql.org; Thu, 30 Jun 2022 20:54:47 +0000 Received: by mail-pj1-x102c.google.com with SMTP id b12-20020a17090a6acc00b001ec2b181c98so4339227pjm.4 for ; Thu, 30 Jun 2022 13:54:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=timescale.com; s=google; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=GLBju+hAegpkANwQnDzcvnZuRT6OJXAf1fN0vXAyyYs=; b=Iyr9IZTQoVE9D+m06OJtuIHvLkVdCkS6RCR+mLmEKvaVYv65/AZ73fPxz2TUfMZfc/ ZEGGrT9NhImvwzMQwH0wDeOLAFeGGdg8Kf69yzPm2BQfgE1A0Sv+oj0QIRJ20OUgUp1I Zzrrk75Sn3bEcjKvSChslkHdjncWVxSRnKzdVwfAEEylbCj2iiJhZ5V83knjrz0eKKpG 5gzpV6WUlnKZ3UKejJDq7L1pxi5VursYNMk+NUX3hs2xCmGEBWc/9KkneUtf1YkS0VX6 JfwOxI3/38lMDjeCcHRQcGzgBbAw+Nuyt2hs1GKplVOnK5WNIsw255vmdz5+nH5xBW0e 5iXw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=GLBju+hAegpkANwQnDzcvnZuRT6OJXAf1fN0vXAyyYs=; b=UjCvj92QvC1ck4kDkqebkApthk7NhHX3yrEzxkmn0RsgS3Zvi6YI6CfVODS2alPkUw QbgHeWKqZTA6UL7e8W/1XLaG6PrO723WLd82bxeXzpDcVA7EXovZ05jl97+mO9xsx2Cr I083iAOrvjATQHAz7xWHhag15ybWGyZkwmh2k/rdrn7v9SKZL7t0oX0v6GVMvpJMkcWZ JFngoYSYMSLPiqpEpMm5NOxYwYa60i4XRSqPb9PrJVK+K54ou9Ft2up3JXdwnPPjfCR6 uljCmYcIyQ5q49Y1sJQbxEawoFXgpB1wjaWe7fAadZ4f92V1vDAgDOsokPJQKaDhlL82 WDiQ== X-Gm-Message-State: AJIora/6j6mXP+i3Wp0Jc+5mfDQ1uiX0Z+PFFy7/4WHR3UQBIxKdBqIG serGMuprTo6puVQn8y+yOOM7hQ== X-Google-Smtp-Source: AGRyM1vm9fHUoEKvyeqNN5NpnTZQif5d1csdzKKjFyd8zpIahwBKQP8UISsLQnZYFIXsdtZVq5ge2A== X-Received: by 2002:a17:902:e382:b0:16a:23a0:9530 with SMTP id g2-20020a170902e38200b0016a23a09530mr17515146ple.128.1656622481118; Thu, 30 Jun 2022 13:54:41 -0700 (PDT) Received: from [192.168.1.21] ([50.39.205.221]) by smtp.gmail.com with ESMTPSA id l11-20020a170903120b00b0016b953872a7sm5664522plh.201.2022.06.30.13.54.40 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 30 Jun 2022 13:54:40 -0700 (PDT) Message-ID: <6bc283b6-11e6-94a7-14fb-cb91da5d6369@timescale.com> Date: Thu, 30 Jun 2022 13:54:39 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1 Subject: Re: [Proposal] Global temporary tables Content-Language: en-US To: Andres Freund , Robert Haas Cc: Greg Stark , Pavel Stehule , Justin Pryzby , wenjing@gmail.com, Andrew Bille , Tony Zhu , PostgreSQL Hackers References: <20220227002111.GA25269@telsasoft.com> <20220227041304.mnimeqkhwktrjyht@alap3.anarazel.de> <20220302211759.k3y2bcfchkukjt7y@alap3.anarazel.de> <20220303212059.fpmgkv4vf2ai4jda@alap3.anarazel.de> From: Jacob Champion In-Reply-To: <20220303212059.fpmgkv4vf2ai4jda@alap3.anarazel.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 3/3/22 13:20, Andres Freund wrote: > On 2022-03-03 16:07:37 -0500, Robert Haas wrote: >> I agree that the feature is desirable, but I think getting there is >> going to require a huge amount of effort that may amount to a total >> rewrite of the patch. > > Agreed. I think this needs very fundamental design work, and the patch itself > isn't worth reviewing until that's tackled. Given two opinions that the patch can't be effectively reviewed as-is, I will mark this RwF for this commitfest. Anyone up for shepherding the design conversations, going forward? --Jacob