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 1l4NHP-00061Y-6W for pgsql-hackers@arkaria.postgresql.org; Tue, 26 Jan 2021 12:17:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l4NHO-0002cj-30 for pgsql-hackers@arkaria.postgresql.org; Tue, 26 Jan 2021 12:17:06 +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 1l4NHN-0002c9-O9 for pgsql-hackers@lists.postgresql.org; Tue, 26 Jan 2021 12:17:05 +0000 Received: from mail-ot1-x333.google.com ([2607:f8b0:4864:20::333]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1l4NHI-0005PL-NX for pgsql-hackers@postgresql.org; Tue, 26 Jan 2021 12:17:04 +0000 Received: by mail-ot1-x333.google.com with SMTP id n42so15945250ota.12 for ; Tue, 26 Jan 2021 04:17:00 -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=Wpwt6gSHoF5WislAU3YAXZCnz3b5XyUx5JMGfNv1WSs=; b=1BmyXhRt9LRganQGsn8OVPSrhgMbezshZOLFgCdFInUzAoEM7avhVKUQutClGPishp RiW9ZOm7DI8n+kLEkmjtwIQQiV3f1Tylf3UNb5MwiS4sZUDI+wPyZgCzp+cAIQLujVc2 HHPm8btufmb87zMlXOHJDg2XSLspSDWAPuajeSv5HRHvhsUqwYK1K9X2BjdGcOqKyJIU FwxijOBabl1jnMTGcIzQiBtrZWDjFboe8IxkJBhwI+IUUv7SqbJgWIbIiyXOBXBBFO7Y jviplP69O58fSo7B0OXofCnJ5k1+PvXBtpfH+IEOdM6jkhv+p5vxDfWQsyrWTRJRmAdD zatg== 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=Wpwt6gSHoF5WislAU3YAXZCnz3b5XyUx5JMGfNv1WSs=; b=Des3CyuppFHmmknBNCs4GRvDZj07SaJ/kJizXgVQCm3Qcy06ZjIIIXy82a56Mp32s5 Vbu3sJ5PI5lM1SOLo77sHqbkr9vqy/QggKWGym5kj0Ent7za1W454sMuZEi6aYJtgZQi FganmO4+FHahIyie9JeR+zrj+b+RH6rDh9zS+kEUWq9ugp1kFE2Sz66o2EEULCJH1TSJ kMf6OoR7bJ2HH72C+DHgu+n2t3EH60KIQ7jEtuWP4XdiRU+2l+XR3xjgMAJpbEjf4ggN 5dMNKLxPowoq6Hjm9yVyuM7Uv/I3KnZbsQDLeU5SbFRXazXjj4/DcmIye0bkpgrCLNYl VQmg== X-Gm-Message-State: AOAM533f6YWvMsTuG3EwAUlpsTZlb+ymXaYts2hKuYdAx/BLr/sg+XTU nM79AnPgfMdPe35lS6hKC4JeulScfPTvwWTzYWxtWKe95UxevM2wND7hsCb496y9blg4apyN+Hx cD6HvR0dMre6MQ3zzAQi8HvCUq/FGhdIKT5cAfBEYyaqZO7XALnYjeQJssdfKiOtJ/NVGmE76Zf D+zZgF2RxnhyOKhxMlk8bpGBAxxb3nJz3LYQy2SdlVmSDoe7uYoYos X-Google-Smtp-Source: ABdhPJwgukoPH67pgHor6AJV+1GWfJ3Vvosk8xqeoGKJ2RYHFNjzvXVZ69/v75ebOtL47uFXDxvn1wcrlkqBKaL5PcQ= X-Received: by 2002:a9d:3603:: with SMTP id w3mr3667645otb.110.1611663419710; Tue, 26 Jan 2021 04:16:59 -0800 (PST) MIME-Version: 1.0 References: <7990518c-3dd3-4f30-c5e1-e094f6126e9a@postgresfriends.org> In-Reply-To: <7990518c-3dd3-4f30-c5e1-e094f6126e9a@postgresfriends.org> From: Simon Riggs Date: Tue, 26 Jan 2021 12:16:48 +0000 Message-ID: Subject: Re: WIP: System Versioned Temporal Table To: Vik Fearing Cc: Ryan Lambert , Masahiko Sawada , Surafel Temesgen , Michael Paquier , =?UTF-8?Q?R=C3=A9mi_Lapeyre?= , Eli Marmor , David Steele , 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 Tue, Jan 26, 2021 at 11:33 AM Vik Fearing wrote: > > On 1/11/21 3:02 PM, Simon Riggs wrote: > > * UPDATE foo SET start_timestamp = DEFAULT should fail but currently doesn't > > I'm still in the weeds of reviewing this patch, but why should this > fail? It should not fail. It should not be possible for the user to change the start or end timestamp of a system_time time range, by definition. -- Simon Riggs http://www.EnterpriseDB.com/