On Tue, Apr 8, 2025, at 2:15 PM, Tom Lane wrote:
> There is nothing whatsoever that is helpful about referring to AoE,
> and if anything, you just made it even clearer that nobody knows
> what that means.
Agreed. Maybe that is a good idea to put a countdown timer [1] in the website
([2] or a new p
On Tue, Apr 08, 2025 at 11:24:39AM -0500, Nathan Bossart wrote:
> I always forget if AoE is UTC+12 or UTC-12. [...]
One isn't supposed to think "is the freeze on everywhere", just "is the
freeze on for me" and "is the freeze on for this particular contribution
(check the date header)".
Nico
--
On Tue, Apr 8, 2025 at 10:13 PM Daniel Gustafsson wrote:
>
> I find both of the above needlessly confusing when we instead could use UTC
> which is a more universally understood concept.
Indeed, that's what the "U" stands for, after all. :-)
--
John Naylor
Amazon Web Services
On Wed, 9 Apr 2025 at 03:54, Bruce Momjian wrote:
> We did have this discussion when AoE was chosen for PG 18 and the idea
> was that as long as it is before April 18 midnight wherever you are, it
> is not feature freeze yet.
I think it maybe once made sense for the moment to stop accepting new
p
On 2025-04-08 Tu 11:45 AM, Peter Geoghegan wrote:
On Tue, Apr 8, 2025 at 11:20 AM Nathan Bossart wrote:
+1 for UTC.
+1, I think that AoE is needlessly obscure
+1
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
On Tue, Apr 08, 2025 at 05:13:15PM +0200, Daniel Gustafsson wrote:
>> On 8 Apr 2025, at 16:59, Bruce Momjian wrote:
>> Frankly, I think the name "anywhere on Earth" is confusing, since it
>> really is "everywhere on Earth":
>
> I find both of the above needlessly confusing when we instead could u
Ashutosh Bapat writes:
> Any timezone based deadline might be seen as unfair to those for whom
> that time falls in their respective nights. AoE removes that
> unfairness.
... only with an interpretation of AoE that is shared by nobody.
It's quite clear that everyone else on this thread reads the
On Tue, Apr 8, 2025 at 9:30 PM Peter Eisentraut wrote:
>
> On 08.04.25 16:59, Bruce Momjian wrote:
> > On Tue, Apr 8, 2025 at 10:36:45AM -0400, Bruce Momjian wrote:
> >> Since we recorded feature freeze as April 8, 2025 0:00 AoE (anywhere on
> >> Earth):
> >>
> >>
> >> https://wiki.postgres
On Tue, Apr 8, 2025 at 12:29 PM Andrew Dunstan wrote:
> The fact that there is this confusion is an indication that the AoE
> experiment is a failure. If it's not obvious, and people have to think
> about it, then it's not working. And I bet there is a huge number of
> people who have never even h
On Tue, Apr 8, 2025 at 11:45:09AM -0400, Peter Geoghegan wrote:
> On Tue, Apr 8, 2025 at 11:20 AM Nathan Bossart
> wrote:
> > +1 for UTC.
>
> +1, I think that AoE is needlessly obscure
We did have this discussion when AoE was chosen for PG 18 and the idea
was that as long as it is before April
On 2025-04-08 Tu 12:11 PM, Bruce Momjian wrote:
On Tue, Apr 8, 2025 at 06:00:27PM +0200, Peter Eisentraut wrote:
On 08.04.25 16:59, Bruce Momjian wrote:
On Tue, Apr 8, 2025 at 10:36:45AM -0400, Bruce Momjian wrote:
Since we recorded feature freeze as April 8, 2025 0:00 AoE (anywhere on
Ear
On Tue, Apr 08, 2025 at 06:00:27PM +0200, Peter Eisentraut wrote:
> On 08.04.25 16:59, Bruce Momjian wrote:
>> Anywhere on Earth (AoE) is a calendar designation that indicates
>> that a period expires when the date passes everywhere on Earth.
>
> Yes, that works intuitively when you spec
On 08/04/2025 19:11, Bruce Momjian wrote:
On Tue, Apr 8, 2025 at 06:00:27PM +0200, Peter Eisentraut wrote:
On 08.04.25 16:59, Bruce Momjian wrote:
On Tue, Apr 8, 2025 at 10:36:45AM -0400, Bruce Momjian wrote:
Since we recorded feature freeze as April 8, 2025 0:00 AoE (anywhere on
Earth):
On Tue, Apr 8, 2025 at 06:00:27PM +0200, Peter Eisentraut wrote:
> On 08.04.25 16:59, Bruce Momjian wrote:
> > On Tue, Apr 8, 2025 at 10:36:45AM -0400, Bruce Momjian wrote:
> > > Since we recorded feature freeze as April 8, 2025 0:00 AoE (anywhere on
> > > Earth):
> > >
> > >
> > > https://wi
On 4/8/25 11:20, Nathan Bossart wrote:
On Tue, Apr 08, 2025 at 05:13:15PM +0200, Daniel Gustafsson wrote:
On 8 Apr 2025, at 16:59, Bruce Momjian wrote:
Frankly, I think the name "anywhere on Earth" is confusing, since it
really is "everywhere on Earth":
I find both of the above needlessly con
On 08.04.25 16:59, Bruce Momjian wrote:
On Tue, Apr 8, 2025 at 10:36:45AM -0400, Bruce Momjian wrote:
Since we recorded feature freeze as April 8, 2025 0:00 AoE (anywhere on
Earth):
https://wiki.postgresql.org/wiki/PostgreSQL_18_Open_Items#Important_Dates
https://www.timeandda
On Tue, Apr 8, 2025 at 11:20 AM Nathan Bossart wrote:
> +1 for UTC.
+1, I think that AoE is needlessly obscure
--
Peter Geoghegan
> On 8 Apr 2025, at 16:59, Bruce Momjian wrote:
>
> On Tue, Apr 8, 2025 at 10:36:45AM -0400, Bruce Momjian wrote:
>> Since we recorded feature freeze as April 8, 2025 0:00 AoE (anywhere on
>> Earth):
>>
>> https://wiki.postgresql.org/wiki/PostgreSQL_18_Open_Items#Important_Dates
>> https://www.
Daniel Gustafsson writes:
> On 8 Apr 2025, at 16:59, Bruce Momjian wrote:
>> Frankly, I think the name "anywhere on Earth" is confusing, since it
>> really is "everywhere on Earth":
> I find both of the above needlessly confusing when we instead could use UTC
> which is a more universally unders
On Tue, Apr 8, 2025 at 10:36:45AM -0400, Bruce Momjian wrote:
> Since we recorded feature freeze as April 8, 2025 0:00 AoE (anywhere on
> Earth):
>
>
> https://wiki.postgresql.org/wiki/PostgreSQL_18_Open_Items#Important_Dates
> https://www.timeanddate.com/time/zones/aoe
>
> and it i
20 matches
Mail list logo
