public inbox for [email protected]
help / color / mirror / Atom feedRe: PG-15.6: timeout parameters erroring out
6+ messages / 3 participants
[nested] [flat]
* Re: PG-15.6: timeout parameters erroring out
@ 2025-02-10 10:36 Mukesh Tanuku <[email protected]>
2025-02-10 12:39 ` Re: PG-15.6: timeout parameters erroring out rob stone <[email protected]>
0 siblings, 1 reply; 6+ messages in thread
From: Mukesh Tanuku @ 2025-02-10 10:36 UTC (permalink / raw)
To: David G. Johnston <[email protected]>; +Cc: Tom Lane <[email protected]>; [email protected] <[email protected]>
Thanks for your quick responses.
I have just added the session related timeout parameters in the
postgresql.conf file also tried tweaking with different values/patterns
like ('1min', '1 min', 80000, 10s, '10s', '10 s')
but i get an immediate error after reloading the configuration file.
*postgres.log file*
2025-02-10 10:27:10.748 GMT [934108] LOG: received SIGHUP, reloading
configuration files
2025-02-10 10:27:10.749 GMT [934108] LOG: parameter
"idle_in_transaction_session_timeout" changed to "80000"
2025-02-10 10:27:16.117 GMT [2531150] ERROR: trailing junk after numeric
literal at or near "80s" at character 43
2025-02-10 10:27:16.117 GMT [2531150] STATEMENT: SET
idle_in_transaction_session_timeout = 80s
though we are not firing any SQL statements explicitly we see this error.
i guess something else is the issue other than spacing.
Regards
Mukesh Tanuku
On Mon, Feb 10, 2025 at 10:38 AM David G. Johnston <
[email protected]> wrote:
> On Sunday, February 9, 2025, Tom Lane <[email protected]> wrote:
>
>> Mukesh Tanuku <[email protected]> writes:
>> > We unabled the postgres timeout parameters in the postgresql.conf file
>>
>> > *idle_in_transaction_session_timeout = '1min'idle_session_timeout =
>> '5min'*
>>
> Did you actually run them together on one line like that?
>
>
>>
> I think that is an email client artifact, dealing with RTF or something.
>
> I do agree too much is missing here. The only known errors involve SET
> which configuration file settings don’t use. And those errors are indeed
> the lack of quoting.
>
> The lack of space I mentioned earlier, in the config text literal, is fine.
>
> David J.
>
>
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: PG-15.6: timeout parameters erroring out
2025-02-10 10:36 Re: PG-15.6: timeout parameters erroring out Mukesh Tanuku <[email protected]>
@ 2025-02-10 12:39 ` rob stone <[email protected]>
2025-02-10 13:34 ` Re: PG-15.6: timeout parameters erroring out Mukesh Tanuku <[email protected]>
0 siblings, 1 reply; 6+ messages in thread
From: rob stone @ 2025-02-10 12:39 UTC (permalink / raw)
To: Mukesh Tanuku <[email protected]>; [email protected]
On Mon, 2025-02-10 at 16:06 +0530, Mukesh Tanuku wrote:
> Thanks for your quick responses.
>
> I have just added the session related timeout parameters in the
> postgresql.conf file also tried tweaking with different
> values/patterns like ('1min', '1 min', 80000, 10s, '10s', '10 s')
>
> but i get an immediate error after reloading the configuration file.
>
> postgres.log file
> 2025-02-10 10:27:10.748 GMT [934108] LOG: received SIGHUP, reloading
> configuration files
> 2025-02-10 10:27:10.749 GMT [934108] LOG: parameter
> "idle_in_transaction_session_timeout" changed to "80000"
> 2025-02-10 10:27:16.117 GMT [2531150] ERROR: trailing junk after
> numeric literal at or near "80s" at character 43
> 2025-02-10 10:27:16.117 GMT [2531150] STATEMENT: SET
> idle_in_transaction_session_timeout = 80s
>
> though we are not firing any SQL statements explicitly we see this
> error.
>
> i guess something else is the issue other than spacing.
>
>
I'd say that 934108 is the config file reload and that 2531150 is from
somebody running psql from a shell or SQL code coming out from an
application.
>
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: PG-15.6: timeout parameters erroring out
2025-02-10 10:36 Re: PG-15.6: timeout parameters erroring out Mukesh Tanuku <[email protected]>
2025-02-10 12:39 ` Re: PG-15.6: timeout parameters erroring out rob stone <[email protected]>
@ 2025-02-10 13:34 ` Mukesh Tanuku <[email protected]>
2025-02-10 13:36 ` Re: PG-15.6: timeout parameters erroring out Mukesh Tanuku <[email protected]>
2025-02-10 16:00 ` Re: PG-15.6: timeout parameters erroring out Tom Lane <[email protected]>
0 siblings, 2 replies; 6+ messages in thread
From: Mukesh Tanuku @ 2025-02-10 13:34 UTC (permalink / raw)
To: rob stone <[email protected]>; +Cc: [email protected]
Thanks for clarifying, got it.
Is this issue specifically reported in only the PG 15 version? more syntax
sensitivity.
On Mon, Feb 10, 2025 at 6:09 PM rob stone <[email protected]> wrote:
>
>
> On Mon, 2025-02-10 at 16:06 +0530, Mukesh Tanuku wrote:
> > Thanks for your quick responses.
> >
> > I have just added the session related timeout parameters in the
> > postgresql.conf file also tried tweaking with different
> > values/patterns like ('1min', '1 min', 80000, 10s, '10s', '10 s')
> >
> > but i get an immediate error after reloading the configuration file.
> >
> > postgres.log file
> > 2025-02-10 10:27:10.748 GMT [934108] LOG: received SIGHUP, reloading
> > configuration files
> > 2025-02-10 10:27:10.749 GMT [934108] LOG: parameter
> > "idle_in_transaction_session_timeout" changed to "80000"
> > 2025-02-10 10:27:16.117 GMT [2531150] ERROR: trailing junk after
> > numeric literal at or near "80s" at character 43
> > 2025-02-10 10:27:16.117 GMT [2531150] STATEMENT: SET
> > idle_in_transaction_session_timeout = 80s
> >
> > though we are not firing any SQL statements explicitly we see this
> > error.
> >
> > i guess something else is the issue other than spacing.
> >
> >
>
> I'd say that 934108 is the config file reload and that 2531150 is from
> somebody running psql from a shell or SQL code coming out from an
> application.
>
>
>
> >
>
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: PG-15.6: timeout parameters erroring out
2025-02-10 10:36 Re: PG-15.6: timeout parameters erroring out Mukesh Tanuku <[email protected]>
2025-02-10 12:39 ` Re: PG-15.6: timeout parameters erroring out rob stone <[email protected]>
2025-02-10 13:34 ` Re: PG-15.6: timeout parameters erroring out Mukesh Tanuku <[email protected]>
@ 2025-02-10 13:36 ` Mukesh Tanuku <[email protected]>
1 sibling, 0 replies; 6+ messages in thread
From: Mukesh Tanuku @ 2025-02-10 13:36 UTC (permalink / raw)
To: rob stone <[email protected]>; +Cc: [email protected]
I see there is some open PR in awx-operator (
https://github.com/ansible/awx/issues/15406) which is related to this. AWX
is connected to DB in my case.
On Mon, Feb 10, 2025 at 7:04 PM Mukesh Tanuku <[email protected]>
wrote:
> Thanks for clarifying, got it.
> Is this issue specifically reported in only the PG 15 version? more syntax
> sensitivity.
>
> On Mon, Feb 10, 2025 at 6:09 PM rob stone <[email protected]> wrote:
>
>>
>>
>> On Mon, 2025-02-10 at 16:06 +0530, Mukesh Tanuku wrote:
>> > Thanks for your quick responses.
>> >
>> > I have just added the session related timeout parameters in the
>> > postgresql.conf file also tried tweaking with different
>> > values/patterns like ('1min', '1 min', 80000, 10s, '10s', '10 s')
>> >
>> > but i get an immediate error after reloading the configuration file.
>> >
>> > postgres.log file
>> > 2025-02-10 10:27:10.748 GMT [934108] LOG: received SIGHUP, reloading
>> > configuration files
>> > 2025-02-10 10:27:10.749 GMT [934108] LOG: parameter
>> > "idle_in_transaction_session_timeout" changed to "80000"
>> > 2025-02-10 10:27:16.117 GMT [2531150] ERROR: trailing junk after
>> > numeric literal at or near "80s" at character 43
>> > 2025-02-10 10:27:16.117 GMT [2531150] STATEMENT: SET
>> > idle_in_transaction_session_timeout = 80s
>> >
>> > though we are not firing any SQL statements explicitly we see this
>> > error.
>> >
>> > i guess something else is the issue other than spacing.
>> >
>> >
>>
>> I'd say that 934108 is the config file reload and that 2531150 is from
>> somebody running psql from a shell or SQL code coming out from an
>> application.
>>
>>
>>
>> >
>>
>
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: PG-15.6: timeout parameters erroring out
2025-02-10 10:36 Re: PG-15.6: timeout parameters erroring out Mukesh Tanuku <[email protected]>
2025-02-10 12:39 ` Re: PG-15.6: timeout parameters erroring out rob stone <[email protected]>
2025-02-10 13:34 ` Re: PG-15.6: timeout parameters erroring out Mukesh Tanuku <[email protected]>
@ 2025-02-10 16:00 ` Tom Lane <[email protected]>
2025-02-10 16:08 ` Re: PG-15.6: timeout parameters erroring out Mukesh Tanuku <[email protected]>
1 sibling, 1 reply; 6+ messages in thread
From: Tom Lane @ 2025-02-10 16:00 UTC (permalink / raw)
To: Mukesh Tanuku <[email protected]>; +Cc: rob stone <[email protected]>; [email protected]
Mukesh Tanuku <[email protected]> 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
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: PG-15.6: timeout parameters erroring out
2025-02-10 10:36 Re: PG-15.6: timeout parameters erroring out Mukesh Tanuku <[email protected]>
2025-02-10 12:39 ` Re: PG-15.6: timeout parameters erroring out rob stone <[email protected]>
2025-02-10 13:34 ` Re: PG-15.6: timeout parameters erroring out Mukesh Tanuku <[email protected]>
2025-02-10 16:00 ` Re: PG-15.6: timeout parameters erroring out Tom Lane <[email protected]>
@ 2025-02-10 16:08 ` Mukesh Tanuku <[email protected]>
0 siblings, 0 replies; 6+ messages in thread
From: Mukesh Tanuku @ 2025-02-10 16:08 UTC (permalink / raw)
To: Tom Lane <[email protected]>; +Cc: rob stone <[email protected]>; [email protected]
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 <[email protected]> wrote:
> Mukesh Tanuku <[email protected]> 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
>
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2025-02-10 16:08 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-02-10 10:36 Re: PG-15.6: timeout parameters erroring out Mukesh Tanuku <[email protected]>
2025-02-10 12:39 ` rob stone <[email protected]>
2025-02-10 13:34 ` Mukesh Tanuku <[email protected]>
2025-02-10 13:36 ` Mukesh Tanuku <[email protected]>
2025-02-10 16:00 ` Tom Lane <[email protected]>
2025-02-10 16:08 ` Mukesh Tanuku <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox