On Mon, Feb 3, 2025 at 12:23 PM Tom Lane wrote:
>
> =?utf-8?Q?=C3=81lvaro?= Herrera writes:
> > On 2025-Feb-03, Robert Treat wrote:
> >> This does seem to come up often enough that it probably is worth being
> >> a bit more explicit about how this works; attached patch attempts
> >> that.
>
> > L
On Mon, 3 Feb 2025 at 11:21, Álvaro Herrera wrote:
> On 2025-Feb-03, Robert Treat wrote:
>
> > This does seem to come up often enough that it probably is worth being
> > a bit more explicit about how this works; attached patch attempts
> > that.
>
> LGTM.
>
> > Note, I dropped the bit about GMT;
=?utf-8?Q?=C3=81lvaro?= Herrera writes:
> On 2025-Feb-03, Robert Treat wrote:
>> This does seem to come up often enough that it probably is worth being
>> a bit more explicit about how this works; attached patch attempts
>> that.
> LGTM.
Hmm, I kind of like the up-front statement that timestampt
On 2025-Feb-03, Robert Treat wrote:
> This does seem to come up often enough that it probably is worth being
> a bit more explicit about how this works; attached patch attempts
> that.
LGTM.
> Note, I dropped the bit about GMT; that change was made ~40 years ago,
> and I suspect it is close to n
On Mon, Jan 27, 2025 at 9:36 AM Tom Lane wrote:
>
> Laurenz Albe writes:
> > On Mon, 2025-01-27 at 07:51 +, PG Doc comments form wrote:
> >> Suggestion: Assuming my understanding is accurate - clarify for the reader
> >> that time zone offset is lost (after conversion to UTC). At risk of stat
On 31.01.25 11:46, Daniel Westermann (DWE) wrote:
I am wondering if there is a reason that the list on top of:
https://www.postgresql.org/docs/devel/monitoring-stats.html
... is not alphabetically ordered?
This was cleaned up most recently in commit 72e0ff2677c. Please check
there if the cur
