Thanks a lot! I will have a look
On Tue, May 22, 2018, 11:53 PM Justin Pryzby wrote:
> On Tue, May 22, 2018 at 03:51:44AM -0700, pavan95 wrote:
> > Please find the output of explain(analyze,buffers) for the whole query in
> > the below link.
>
> > Seq Scan on res_users
On Jan 26, 2018 6:02 AM, "Pavan Teja" <pavan.postgres...@gmail.com> wrote:
On Jan 26, 2018 3:00 AM, "Alvaro Herrera" <alvhe...@alvh.no-ip.org> wrote:
pavan95 wrote:
> Hi Álvaro Herrera,
>
> Please find the corresponding output:
OK, these settings look
On Jan 24, 2018 7:57 PM, "Claudio Freire" wrote:
On Wed, Jan 24, 2018 at 8:50 AM, pavan95
wrote:
> Hello all,
>
> One more interesting observation made by me.
>
> I have ran the below query(s) on production:
>
> SELECT
> relname,
>
Hi David,
If it's yes what needs to be done in order to stabilize this issue??
Thanks in advance.
Regards,
Pavan
On Jan 23, 2018 8:15 PM, "David G. Johnston" <david.g.johns...@gmail.com>
wrote:
> On Tue, Jan 23, 2018 at 7:39 AM, Pavan Teja <pavan.postgres
Yes so many wals are continuing to be produced.
Deleting the wals after a backup of the database.
Yes archiving mode is on. And the warning message in log file is
" checkpoints are frequently occurring (1second apart). Consider increasing
checkpoint_segements parameter".
My doubt is previously