Re: [ADMIN] pg_basebackup blocking all queries with horrible performance

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Lonni J Friedman <netllama(at)gmail(dot)com>, Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>, Jerry Sievers <gsievers19(at)comcast(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [ADMIN] pg_basebackup blocking all queries with horrible performance
Date: 2012-06-20 18:18:39
Message-ID: CA+TgmoYrrx32Qg5BuLFAh+jUrWbLWcZMDg0jgU-Z3BGTKPqg=w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers

On Wed, Jun 20, 2012 at 7:18 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>>>> You agreed to add something like NOSYNC option into START_REPLICATION command?
>>>
>>> I'm on the fence. I was hoping somebody else would chime in with an
>>> opinion as well.
>>
>> +1
>
> Nobody else with any opinion on this? :(

I don't think we really need a NOSYNC flag at this point. Just not
setting the flush location in clients that make a point of flushing in
a timely fashion seems fine.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message wangqi 2012-06-21 03:38:31 about shared_buffer and kernel.shmmax
Previous Message Misa Simic 2012-06-20 16:01:40 Re: View as front-end to function

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2012-06-20 18:20:21 Re: Nasty, propagating POLA violation in COPY CSV HEADER
Previous Message Robert Haas 2012-06-20 18:16:16 Re: Pg default's verbosity?