On Thu, Sep 7, 2023 at 04:41:48PM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> > Uh, yes to the storage part, no to the output part. ;-) Postgres does
> > store the timetz time zone offset, but it doesn't adust it once it is
> > stored so doesn't adjust for the session time zone:
>
> Right
Bruce Momjian writes:
> Uh, yes to the storage part, no to the output part. ;-) Postgres does
> store the timetz time zone offset, but it doesn't adust it once it is
> stored so doesn't adjust for the session time zone:
Right, it just stores a numeric UTC offset.
> Do we want to document this?
On Fri, May 19, 2023 at 06:03:43PM +, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/15/datatype-datetime.html
> Description:
>
> This statement in section 8.5.3 states
> "All timezone-aware dates and
On Wed, May 24, 2023 at 09:10:37PM +0200, Erik Wienhold wrote:
> > On 24/05/2023 15:46 CEST Erik Wienhold wrote:
> >
> > Personally, I think it should read cartesian product because cross product
> > is
> > an overloaded term and cartesian product is used more often in the
> > documentation
> >
On Mon, Jun 5, 2023 at 11:03:49PM +, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/14/catalog-pg-class.html
> Description:
>
> In the pg_class documentation [1], the relpages column is described as
On Wed, Sep 6, 2023 at 08:01:30PM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> > On Tue, Jul 11, 2023 at 07:31:26AM -0700, David G. Johnston wrote:
> >> I think the complaint is that someone seeing the behavior in the wild
> >> comes to
> >> this order-of-operations and doesn't see that the
