Re: INTERVAL MINUTE TO SECOND didn't do what I thought it would do

On Wed, Jan 8, 2025 at 3:07 PM Adrian Klaver wrote: > > > On 1/8/25 11:58 AM, Ron Johnson wrote: > > On Wed, Jan 8, 2025 at 2:43 PM Adrian Klaver > > wrote: > > > > > > I'd hoped that ::INTERVAL MINUTE TO SECOND would do the trick, but > > > MINUTE TO

Re: INTERVAL MINUTE TO SECOND didn't do what I thought it would do

On 1/8/25 11:58 AM, Ron Johnson wrote: On Wed, Jan 8, 2025 at 2:43 PM Adrian Klaver > wrote: > I'd hoped that ::INTERVAL MINUTE TO SECOND would do the trick, but > MINUTE TO SECOND seems to be ignored.  From here: https://www.postgres

Re: INTERVAL MINUTE TO SECOND didn't do what I thought it would do

On Wed, Jan 8, 2025 at 2:43 PM Adrian Klaver wrote: > > > On 1/8/25 11:00 AM, Ron Johnson wrote: > > PG 14.13 > > > > The goal of "(now() - query_start)::INTERVAL MINUTE TO SECOND" column is > > to see how many minutes and seconds ago that the query started. (Why? > > Because that's useful to me

Re: INTERVAL MINUTE TO SECOND didn't do what I thought it would do

On 1/8/25 11:00 AM, Ron Johnson wrote: PG 14.13 The goal of "(now() - query_start)::INTERVAL MINUTE TO SECOND" column is to see how many minutes and seconds ago that the query started.  (Why? Because that's useful to me, and the people I show the output to when queries run for more than a

INTERVAL MINUTE TO SECOND didn't do what I thought it would do

PG 14.13 The goal of "(now() - query_start)::INTERVAL MINUTE TO SECOND" column is to see how many minutes and seconds ago that the query started. (Why? Because that's useful to me, and the people I show the output to when queries run for more than a few minutes. We don't need to see hours and da