Re: ago(interval) → timestamptz
| От | Quan Zongliang | 
|---|---|
| Тема | Re: ago(interval) → timestamptz | 
| Дата | |
| Msg-id | de0a33e0-97b9-45f1-9cbe-949db62943fe@yeah.net обсуждение исходный текст  | 
		
| Ответ на | Re: ago(interval) → timestamptz (Laurenz Albe <laurenz.albe@cybertec.at>) | 
| Список | pgsql-hackers | 
On 11/4/25 1:55 PM, Laurenz Albe wrote:
> On Mon, 2025-11-03 at 22:36 +0100, Florents Tselai wrote:
>> I realize this will get some "you can easily implement this yourself” pushback,
>> But I keep seeing and writing a lot of WHERE ts > now() - interval '1 day' expressions.
> 
> You can easily implement this yourself...
> Also, there already is something similar in the shape of 'yesterday'::timestamptz.
> Moreover, a good percentage of the users would instead need ago(interval) -> timestamp.
> 
> So I'd say that the added value is marginal, and I personally find
> 
>     current_timestamp - INTERVAL '1' DAY
> 
> more readable and more SQL standard compliant than
> 
>     ago('1 day')
> 
now() - interval '1 day' is merely an example. In fact, we could use any 
time. For example
   now() - interval '10 day 5 hours 21 minutes'
This is beyond the scope of what yesterday() can support.
Therefore, I think this patch can be accepted. Make the user's operation 
more convenient.
--
Quan Zongliang
> Yours,
> Laurenz Albe
> 
		
	В списке pgsql-hackers по дате отправления: