maximum aggregate of time type returning incorrect value

[the6campbells]

Version: 0.160

The expected projected value is 23:59:30 and not the returned value of 12:00:00

select max( vtm.ctm ) from postgres_cert.public.vtm

source data
rnum ctm
0
1 00:00:00
2 12:00:00
3 23:59:30

describe of table

Column Type Comment
rnum integer
ctm time

[fiedukow]

I'll try to reproduce that.

[ArturGajowy]

@fiedukow did you manage? :)

[fiedukow]

Yes.
It seems to be caused by #7122
Closing as this new ticket describes underlying problem much better.

[the6campbells]

The discussion thread #7122 seems to about Presto and timestamp and time zone semantics. Was not clear how that ties into incorrect aggregation of a TIME type. Please review and reopen as applicable.

[fiedukow]

time semantic is aligned with timestamp semantic.
time with time zone semantic is aligned with timestamp with time zone semantic.

As such, time (w/o TZ) does apply use timezone to the value. The semantic may differ between connectors as well. Maybe I closed this a little bit to early as this may also be connected to wrong behaviour on PostgreSQL connector side. I think that this should be retested after fixing semantic in Presto though, as check on Presto side is definitely required to fix other problems properly.

Sorry for closing that to early. Leaving open and assigned to myself as I'm going to dive into TIMESTAMP problem now.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.