On Thu, Sep 13, 2018 at 7:05 PM Chris Williams wrote:
> We just have a few ruby on rails applications connected to the database,
> and don't really have any long running or heavy queries and the db is under
> very light load, so I don't understand why it takes so long to shutdown.
> We do have a
On Tue, Jun 19, 2018 at 12:16 AM Benjamin Scherrey <
scher...@proteus-tech.com> wrote:
> I would also add that AWS' I/O capabilities are quite poor and expensive.
> I assume that you have tried purchasing additional IOOPs on that setup to
> see whether you got an expected speed up? If not you shou
On Mon, Jun 18, 2018 at 7:23 PM Andres Freund wrote:
> > So far it's been almost two months of investigation
> > and people at AWS technical support don't seem to find the cause. I think
> > it could be related to Postgres and the number of schema/tables in the
> > database, that's why I post thi
Hi,
I'm experiencing high WriteLatency levels in a Postgres server 9.3.20
hosted in Amazon RDS. So far it's been almost two months of investigation
and people at AWS technical support don't seem to find the cause. I think
it could be related to Postgres and the number of schema/tables in the
datab
On Wed, Mar 28, 2018 at 2:58 AM, Laurenz Albe
wrote:
> Juan Manuel Cuello wrote:
> > I have a postgresql database with around 4000 schemas. Each schema has
> around
> > the same 65 tables. There are 8 processes connected to the database (it
> is a web app).
> > Each
I have a postgresql database with around 4000 schemas. Each schema has
around the same 65 tables. There are 8 processes connected to the database
(it is a web app). Each process has only one direct connection to the
database (no connection pool).
Everything works ok until a new schema (with all it
