Hi,
The following talk describes an issue with how Linux may handle memory
allocation for Postgres. The issue may cause many hundreds of megabytes
not being released in some cases.
PostgreSQL and RAM usage [Feb 27, 2017]
https://www.youtube.com/watch?v=EgQCxERi35A
see between minutes 33 and 3
Then we should find like if there are any idle sessions with uncommitted
transactions. Those might be the culprits.
Regards,
Pavan
--
Sent from:
http://www.postgresql-archive.org/PostgreSQL-performance-f2050081.html
On Tue, Jan 23, 2018 at 10:54:01PM -0700, pavan95 wrote:
> If you are finding some sessions then of course your database is
> perfectly alright. As sessions won't consume any memory.
Those have a cost as well when building transaction snapshots. Too much
of them is no good either, let's not forg
Hi Rambabu,
If you are finding some sessions then of course your database is
perfectly alright. As sessions won't consume any memory.
Kindly specify the issue briefly.
Regards,
Pavan
--
Sent from:
http://www.postgresql-archive.org/PostgreSQL-performance-f2050081.html
On Tue, Jan 23, 2018 at 5:59 AM, Rambabu V wrote:
> > cat PostgreSQL-2018-01-23_06.csv|grep FATAL
What about ERROR, not just FATAL? Or grep for "out of memory"
>> *$ free -mh*
>> total used free sharedbuffers cached
>> Mem: 58G58G
On Tue, 2018-01-23 at 19:29 +0530, Rambabu V wrote:
> Any Update, this is continuously hitting our production database.
>
> > OOM error not recording in server level, it is only recording in our
> > database logs.
> >
> > below is the error message:
> >
> > cat PostgreSQL-2018-01-23_06.csv|
Am 23.01.2018 um 14:59 schrieb Rambabu V:
total used free shared buffers cached
Mem: 58G 58G 358M 16G 3.6M 41G
-/+ buffers/cache: 16G 42G
Swap: 9.5G 687M 8.9G
*postgresql.conf parametes:*
*
Hi Laurenz,
Any Update, this is continuously hitting our production database.
Regards,
Rambabu Vakada,
PostgreSQL DBA.
On Tue, Jan 23, 2018 at 6:12 PM, Rambabu V wrote:
> Hi Laurenz,
>
> OOM error not recording in server level, it is only recording in our
> database logs.
>
> below is the err
Rambabu V wrote:
> we are seeing idle sessions consuming memory in our database, could you
> please help me
> how much memory an idle session can use max and how can we find how much
> work_mem
> consuming for single process.
>
> we are getting out of memory error,for this i'm asking above quest
Hi Team,
we are seeing idle sessions consuming memory in our database, could you
please help me how much memory an idle session can use max and how can we
find how much work_mem consuming for single process.
we are getting out of memory error,for this i'm asking above questions.
Regards,
Ramba
10 matches
Mail list logo