pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
Cc: andres@anarazel.de
Cc: robertmhaas@gmail.com
Cc: tgl@sss.pgh.pa.us
Cc: michael.paquier@gmail.com
Cc: david@pgmasters.net
Cc: Jim.Nasby@bluetreble.com
Cc: craig@2ndquadrant.com
Cc: pgsql-hackers@postgresql.org
Subject: Re: Protect syscache from bloating with negative cache entries
Date: Wed, 7 Mar 2018 08:01:38 -0300
Message-ID: <20180307110138.qp3wsav7ka43qrlj@alvherre.pgsql> (raw)
In-Reply-To: <20180307.172545.231972323.horiguchi.kyotaro@lab.ntt.co.jp>

The thing that comes to mind when reading this patch is that some time
ago we made fun of other database software, "they are so complicated to
configure, they have some magical settings that few people understand
how to set".  Postgres was so much better because it was simple to set
up, no magic crap.  But now it becomes apparent that that only was so
because Postgres sucked, ie., we hadn't yet gotten to the point where we
*needed* to introduce settings like that.  Now we finally are?

I have to admit being a little disappointed about that outcome.

I wonder if this is just because we refuse to acknowledge the notion of
a connection pooler.  If we did, and the pooler told us "here, this
session is being given back to us by the application, we'll keep it
around until the next app comes along", could we clean the oldest
inactive cache entries at that point?  Currently they use DISCARD for
that.  Though this does nothing to fix hypothetical cache bloat for
pg_dump in bug #14936.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services




view thread (272+ messages)  latest in thread

Message-ID: <20180307110138.qp3wsav7ka43qrlj@alvherre.pgsql>
Permalink:  ../20180307110138.qp3wsav7ka43qrlj@alvherre.pgsql/
Also on:    postgresql.org/message-id/20180307110138.qp3wsav7ka43qrlj@alvherre.pgsql

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: alvherre@alvh.no-ip.org, horiguchi.kyotaro@lab.ntt.co.jp, andres@anarazel.de, robertmhaas@gmail.com, tgl@sss.pgh.pa.us, michael.paquier@gmail.com, david@pgmasters.net, Jim.Nasby@bluetreble.com, craig@2ndquadrant.com
  Subject: Re: Protect syscache from bloating with negative cache entries
  In-Reply-To: <20180307110138.qp3wsav7ka43qrlj@alvherre.pgsql>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox