Re: Re: BUG #13685: Archiving while idle every archive_timeout with wal_level hot_standby

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: BUG #13685: Archiving while idle every archive_timeout with wal_level hot_standby
Date: 2016-02-08 14:24:31
Message-ID: CAA4eK1KZ72BLdx8ByzGAv9zSmJ1R7EG1_b+z+38781AuBsP6-A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Mon, Feb 8, 2016 at 12:28 PM, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
wrote:
>
>
> >> /*
> >> + * Fetch the progress position before taking any WAL insert
lock. This
> >> + * is normally an operation that does not take long, but leaving
this
> >> + * lookup out of the section taken an exclusive lock saves a
couple
> >> + * of instructions.
> >> + */
> >> + progress_lsn = GetProgressRecPtr();
> >
> > too long for my taste. How about:
> > /* get progress, before acuiring insert locks to shorten locked section
*/
>
> Check.
>

What is the need of holding locks one-by-one during checkpoint when
we anyway are going to take lock on all the insertion slots.

+ * to not rely on taking an exclusive lock an all the WAL insertion locks,

/an all/on all

With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message dominik.kosiorek 2016-02-08 15:11:07 BUG #13934: wrong result of split_part with char value
Previous Message Michael Paquier 2016-02-08 11:47:36 Re: Re: BUG #13685: Archiving while idle every archive_timeout with wal_level hot_standby

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2016-02-08 14:32:31 process type escape for log_line_prefix
Previous Message Andres Freund 2016-02-08 14:24:29 Re: 9.5 new setting "cluster name" and logging