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 1lhHe8-0004A8-Uu for pgsql-docs@arkaria.postgresql.org; Thu, 13 May 2021 20:09:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lhHe7-0004Rj-Nt for pgsql-docs@arkaria.postgresql.org; Thu, 13 May 2021 20:09:23 +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 1lhHe7-0004Ra-Fc for pgsql-docs@lists.postgresql.org; Thu, 13 May 2021 20:09:23 +0000 Received: from mail-pj1-x1033.google.com ([2607:f8b0:4864:20::1033]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lhHe4-0008NZ-V0 for pgsql-docs@lists.postgresql.org; Thu, 13 May 2021 20:09:22 +0000 Received: by mail-pj1-x1033.google.com with SMTP id o17-20020a17090a9f91b029015cef5b3c50so156799pjp.4 for ; Thu, 13 May 2021 13:09:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=AjPh9KMn/rgNaQQoN2Kq7SvOpIZoI+kRRLEj2NM99Ss=; b=kfKJFtt5c9D+W7OUQ06X38VRTPjZQiyJCm8rHILuOP5sDqX4GVawZbwmZKbfE1G9lu cTMYPWpC5u/bWZTX4ZmE99DM1+MbmFG8sWLWaFalain4mt8kotkUTeWyB8XgblqiTZEF IVAsdZAFISMlGFGHdzTmf6sm+LfCEu0EwgqW06gUtZMl8N1KrtVxH+1tLwhhirqmI/rW XfkWDYu2e3IIJJAw/2l96hHNXBn/Wpl1xcW3YVGYEFED9ByYKIIDj+IVYtz9kNX+FIjK KBAwTd9UFvBRBTywtotJbxsGr6ztbyNoIRtqftqnNf2oHOlH1qm3fCjEeEepfPWPoGdY j+NA== 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=AjPh9KMn/rgNaQQoN2Kq7SvOpIZoI+kRRLEj2NM99Ss=; b=M9a2n3rzAwAk9QeQvYPK8VSr9dY//3n/6sSSZEfihE0j78v57GwTD8HkbwsPgLCXVl CtwMFGwNNvdMoIWLiouMhEWGP42zMafm+GxS/eaqcxw2qNsnBuwKF0xbQXiSEJ1vr56S EQ22dEbPydRuTizm3+d9c8pCfSy47TWOsW4W9w0YOHIRfPLi/B86LA8K+5GuwZZca7wN irUugt1KLQBFjNRty9Ltp7Cd4t591ybbXHJYlX/NwH8Oi2blyZkrD6OMtrueN3et8SZH lLF8fexQy5501OCUz5yxzJ4cngLIAHpGt+z032zVInCGmTs3L7clkzh2CvAtlZtK2Qsg 2VYA== X-Gm-Message-State: AOAM5309LlxxDQdMCnFtc66b7QhM8MjG9G+sBv3Uy/EiFBIxcLJ2VPRZ /NrhPgCzKoV7F6tX5ON56d1shqkk7jS2xb36W5s= X-Google-Smtp-Source: ABdhPJxrv9IXxR334yMEPqFCGHapU9jHBLSxIPQpsvOZSaY7sM7kx6E0iLeFr5+lrp/1TUwMAWrYno7va+EEbV66qws= X-Received: by 2002:a17:90a:fb97:: with SMTP id cp23mr6921842pjb.169.1620936558723; Thu, 13 May 2021 13:09:18 -0700 (PDT) MIME-Version: 1.0 References: <88C5909B-A649-4E0C-9037-19CCAED9944A@yugabyte.com> In-Reply-To: <88C5909B-A649-4E0C-9037-19CCAED9944A@yugabyte.com> From: "David G. Johnston" Date: Thu, 13 May 2021 13:09:01 -0700 Message-ID: Subject: =?UTF-8?B?UmU6IFdoZXJlIGlzIHRoZSBzeW50YXggIjwtMDg+KzA4IiBkb2N1bWVudGVk4oCUY29tZQ==?= =?UTF-8?B?cyBmcm9tICJzZWxlY3QgY3VycmVudF9zZXR0aW5nKCd0aW1lem9uZScpIg==?= To: Bryn Llewellyn Cc: Pg Docs Content-Type: multipart/alternative; boundary="000000000000c9473c05c23bb37c" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000c9473c05c23bb37c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, May 13, 2021 at 12:38 PM Bryn Llewellyn wrote: > =C2=AB POSIX has positive signs west of Greenwich, but many people expect > positive signs east of Greenwich. =C2=BB > > Is there a setting that I can do to make "set timezone =3D '-08:00'" trea= t > it as a request to set the negative value that I said? > That ultimately comes from the appendix. https://www.postgresql.org/docs/current/datetime-posix-timezone-specs.html As noted here: https://www.postgresql.org/docs/current/datatype-datetime.html#DATATYPE-TIM= EZONES There are three ways to specify TimeZone in PostgreSQL. You are using the third option and thus are dealing with the caveats noted in the third entry's description and described in detail in the appendix linked to above= . I suggest restricting your use to one of the other two, recommended, options. If you cannot avoid using the third option you must learn and abide by its rules. David J. --000000000000c9473c05c23bb37c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, May 13, 2021 at 12:38 PM Bryn Llewellyn <bryn@yugabyte.com> wrote:
<= /div>
=C2=AB POSIX ha= s positive signs west=C2=A0of Greenwich, but many people expect positive si= gns east=C2=A0of=C2=A0Greenwich. =C2=BB

Is the= re a setting that I can do to make "set timezone =3D '-08:00'&= quot; treat it as a request to set the negative value that I said?

That ultimately comes from the appendix.<= /div>

https://www.postgresql.org/docs/current/da= tetime-posix-timezone-specs.html

As noted here:

https://www.postgresql.org/docs/curre= nt/datatype-datetime.html#DATATYPE-TIMEZONES

There= are three ways to specify TimeZone in PostgreSQL.=C2=A0 You are using the = third option and thus are dealing with the caveats=C2=A0noted in the third = entry's description and described in detail in the appendix linked to a= bove.

I suggest restricting your use to one of the oth= er two, recommended, options.=C2=A0 If you cannot avoid using the third opt= ion you must learn and abide by its rules.

David J.

--000000000000c9473c05c23bb37c--