Hi,
On Thu, Aug 5, 2021 at 11:28 AM Vijaykumar Jain <
vijaykumarjain.git...@gmail.com> wrote:
> On Thu, 5 Aug 2021 at 10:27, Nikhil Shetty wrote:
>
>> Hi,
>>
>> Thank you for the suggestion.
>>
>> We tried by dropping indexes and it worked faster compared to what we saw
>> earlier. We wanted to
Hi,
On Fri, Jun 5, 2020 at 7:07 AM Krzysztof Olszewski
wrote:
> I have problem with one of my Postgres production server. Server works
> fine almost always, but sometimes without any increase of transactions or
> statements amount, machine gets stuck. Cores goes up to 100%, load up to
> 160%.
Hi,
On Fri, May 8, 2020 at 3:53 AM Laurenz Albe
wrote:
> On Fri, 2020-05-08 at 03:47 -0300, Avinash Kumar wrote:
> > > Just set "autovacuum_max_workers" higher.
> >
> > No, that wouldn't help. If you just increase autovacuum_m
Hi,
On Fri, May 8, 2020 at 3:31 AM Laurenz Albe
wrote:
> On Thu, 2020-05-07 at 18:17 -0300, Avinash Kumar wrote:
> > > The nice thing about separate databases is that it is easy to scale
> > > horizontally.
> >
> > Agreed. But, how about autovacuum ? Wo
Hi,
On Thu, May 7, 2020 at 6:08 PM Rory Campbell-Lange
wrote:
> On 07/05/20, Avinash Kumar (avinash.vallar...@gmail.com) wrote:
> > >> Our application serves multiple tenants. Each tenant has the schema
> > >> with a few hundreds of tables and few functions.
> &
Hi,
On Thu, May 7, 2020 at 5:18 PM David G. Johnston
wrote:
> On Thu, May 7, 2020 at 1:05 PM samhitha g
> wrote:
>
>> Our application serves multiple tenants. Each tenant has the schema
>> with a few hundreds of tables and few functions.
>> We have 2000 clients so we have to create 2000
