Re: PG-15.6: timeout parameters erroring out

From: Mukesh Tanuku <mukesh(dot)postgres(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: rob stone <floriparob(at)tpg(dot)com(dot)au>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: PG-15.6: timeout parameters erroring out
Date: 2025-02-10 16:08:45
Message-ID: CAJzgB-GyuGBFMWRaX0Nb_AzLKSC_ZrggTh6yn+RpgF34OFQMxg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thanks for all of you for responding and clarifying things. Really
appreciate it.

We finally confirmed that it is a SET command issue where the AWX
application is firing the query without quotes and it's a known bug from
their end.

Thank you once again.
Regards
Mukesh Tanuku

On Mon, Feb 10, 2025 at 9:30 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Mukesh Tanuku <mukesh(dot)postgres(at)gmail(dot)com> writes:
> > Is this issue specifically reported in only the PG 15 version? more
> syntax
> > sensitivity.
>
> PG 15 and up report the syntax error differently.
>
> regression=# set foo = 15min;
> ERROR: trailing junk after numeric literal at or near "15min"
> LINE 1: set foo = 15min;
> ^
>
> In v14 that'd look like
>
> regression=# set foo = 15min;
> ERROR: syntax error at or near "min"
> LINE 1: set foo = 15min;
> ^
>
> There are variants of this (lack of space between a number and an
> identifier) that will be rejected by 15+ although older versions
> accepted them. But in a SET command I think no version will take it.
>
> regards, tom lane
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Josef Šimánek 2025-02-10 19:45:47 Any plan for minor release?
Previous Message Tom Lane 2025-02-10 16:00:57 Re: PG-15.6: timeout parameters erroring out