RE: Timeout parameters - Mailing list pgsql-hackers

From Tsunakawa, Takayuki
Subject RE: Timeout parameters
Date
Msg-id 0A3221C70F24FB45833433255569204D1FBC7626@G01JPEXMBYT05
Whole thread Raw
In response to RE: Timeout parameters  (MikalaiKeida@ibagroup.eu)
Responses Re: Timeout parameters
RE: Timeout parameters
List pgsql-hackers
From: MikalaiKeida@ibagroup.eu [mailto:MikalaiKeida@ibagroup.eu]
> > For example, OS issues such as abnormally (buggy) slow process scheduling
> or paging/swapping that prevent control from being passed to postgres.  Or,
> abnormally long waits on lwlocks in postgres.  statement_timeout doesn't
> take effect while waiting on a lwlock.  I have experienced both.  And, any
> other issues in the server that we haven't experienced and not predictable.
> 
> For me all mentioned by Takayuki Tsunakawa problems looks like a lack of
> design of end-user application or configuration of DB server. It is not
> a problem of PostgreSQL.

Certainly, my cases could be avoided by the OS and database configuration.  But we cannot say all such problems can be
avoidedby configuration in advance.  The point is to provide a method to get ready for any situation.
 


Regards
Takayuki Tsunakawa






pgsql-hackers by date:

Previous
From: MikalaiKeida@ibagroup.eu
Date:
Subject: RE: Timeout parameters
Next
From: David Rowley
Date:
Subject: Re: Inadequate executor locking of indexes