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 1l0A4q-0001yV-TE for pgsql-hackers@arkaria.postgresql.org; Thu, 14 Jan 2021 21:22:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l0A4p-00062Q-RA for pgsql-hackers@arkaria.postgresql.org; Thu, 14 Jan 2021 21:22:43 +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 1l0A4p-00062G-Eb for pgsql-hackers@lists.postgresql.org; Thu, 14 Jan 2021 21:22:43 +0000 Received: from mail-ot1-x335.google.com ([2607:f8b0:4864:20::335]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1l0A4m-0001vA-3D for pgsql-hackers@postgresql.org; Thu, 14 Jan 2021 21:22:42 +0000 Received: by mail-ot1-x335.google.com with SMTP id o11so6595204ote.4 for ; Thu, 14 Jan 2021 13:22:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xFLY8GCrWaojrRDuRHEc2OZUEb9RmeCSbjtdmwiaM/U=; b=1vEEUVpEZVQqOWS4hmmdykGf8BRHtNbBxX0voZsNx7G7LNMkkzEf5Q+co004YDh+BK dy27VUW553qJGFXEgeDWASwFHWXIHJn5AyMnG63CC15XYCAD0m+mlOYjksDHcUvJsKQe 2eG5NT9WAFgQ+Qm3R0LfkaQO4LWBG3cOrHCpuGwqnbgRu35+4r9WS/9/kF4lx67xqMuu 7ZWDohlghKzxUxYlUnFdjrN7ltGLzj/4DSpt2OouuqySjG1aP2LlVclU7N6cGNGofbT7 kN4+EGAKwn/4q9zjJErXPyTIvs7hBs5jzw/ndGRAI43/9V6sa4LeWH29RXboY1o8TAiX V6rw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xFLY8GCrWaojrRDuRHEc2OZUEb9RmeCSbjtdmwiaM/U=; b=hfWRNcb+4vL63PD9Xm5OseHyRYGRyyiSVcgo5gh/OraHX6Nxm3mTxJOp1RfEy5ixiP QifGu1l5EF2/G5U8/cSAi1cnqRK34zeWhHlqTJMf7J2gdQ/b+T261OdB4OZ2vbdssn4A 8Li36gvAe1SlZoNBBmU2LOblDgnvufJooaLevCRD3GRGXHuVK6nWR0iNsetPKjCItWB9 /3AxV9SNQ1jqTGM0325Hte8rtwLD/Py8SBqdvnIPxupw5cyZOBlXwupXx8j4bpLVnush I77RvJmAZKD2wU30wf/ky2QeOjACqThHUhCiBOphHD7OrKPd+B4G8amVv5GjOW/Vdo16 CvjQ== X-Gm-Message-State: AOAM531lrbN2rrxqF44MycOFB08uAHKIm8MvBhvM2iys86xKm59xDRdU 5fLr0kjbezuDHNTz6KST35S//irka8D0X07ez4yXBxUTIvywC1OAC9tp1wo1jUPJjZb4uOyRWMe jW4auAlhqtd1daVEp8U8QjMnQlH0DX+MDjDkm07YG2nJfONbNHAU3COh2Azpp6hGI4h/xKP6ZyX 3our5xZp3Dq+MMcZQbGyejOvq5pYwUFE/mJH+M8EK9OrYZbd3T7/Oz X-Google-Smtp-Source: ABdhPJyqg75njdhvr5b/7qLMpvztstPJVO1KHV64piz+FbjDicpfAK/vU5QgHv4U/Vtuc3stnSAWOSNsWZce2E1oPU4= X-Received: by 2002:a9d:3603:: with SMTP id w3mr5709285otb.110.1610659357440; Thu, 14 Jan 2021 13:22:37 -0800 (PST) MIME-Version: 1.0 References: <9550e917-c370-36a3-277f-2f25bfc1b497@2ndquadrant.com> <1c0f2169-f949-f5c5-9069-b6d0d7e110a7@pgmasters.net> <00B5FD97-A568-4270-B0CF-59BA7DEEBFEA@lenstra.fr> <20200929054427.GC7117@paquier.xyz> In-Reply-To: From: Simon Riggs Date: Thu, 14 Jan 2021 21:22:26 +0000 Message-ID: Subject: Re: WIP: System Versioned Temporal Table To: Surafel Temesgen Cc: Ryan Lambert , Masahiko Sawada , Michael Paquier , =?UTF-8?Q?R=C3=A9mi_Lapeyre?= , Eli Marmor , David Steele , Vik Fearing , PostgreSQL Hackers , Georgios Content-Type: text/plain; charset="UTF-8" X-CLOUD-SEC-AV-Info: enterprisedb,google_mail,monitor X-CLOUD-SEC-AV-Sent: true X-Gm-Spam: 0 X-Gm-Phishy: 0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Thu, Jan 14, 2021 at 5:46 PM Surafel Temesgen wrote: > On Fri, Jan 8, 2021 at 7:50 PM Ryan Lambert wrote: >> >> I prefer to have them hidden by default. This was mentioned up-thread with no decision, it seems the standard is ambiguous. MS SQL appears to have flip-flopped on this decision [1]. I think the default should be like this: SELECT * FROM foo FOR SYSTEM_TIME AS OF ... should NOT include the Start and End timestamp columns because this acts like a normal query just with a different snapshot timestamp SELECT * FROM foo FOR SYSTEM_TIME BETWEEN x AND y SHOULD include the Start and End timestamp columns since this form of query can include multiple row versions for the same row, so it makes sense to see the validity times -- Simon Riggs http://www.EnterpriseDB.com/