Re: BUG #18470: Time literal accepted in Postgres 15 and below, not accepted in Postgres 16

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: david(dot)perez(dot)ingeniero(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18470: Time literal accepted in Postgres 15 and below, not accepted in Postgres 16
Date: 2024-05-17 21:52:48
Message-ID: 2599239.1715982768@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I wrote:
> So at this point, yeah that's a bug we should fix.
> I'll look into it later if nobody beats me to it.

It is failing because it sees an "unhandled prefix type",
that is ptype still nonzero after the parsing loop
in DecodeTimeOnly. We need to reset ptype, as is done
in the comparable case in DecodeDateTime.

regards, tom lane

Attachment Content-Type Size
fix-bug-18470.patch text/x-diff 5.7 KB

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Haifang Wang (Centific Technologies Inc) 2024-05-17 22:25:34 RE: [EXTERNAL] Re: Windows Application Issues | PostgreSQL | REF # 48475607
Previous Message Tom Lane 2024-05-17 20:39:05 Re: BUG #18468: CREATE TABLE ... LIKE leaves orphaned column reference in extended statistics