Re: [ADMIN] pg_basebackup blocking all queries with horrible performance - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [ADMIN] pg_basebackup blocking all queries with horrible performance
Date
Msg-id CA+TgmoYrrx32Qg5BuLFAh+jUrWbLWcZMDg0jgU-Z3BGTKPqg=w@mail.gmail.com
Whole thread Raw
In response to Re: [ADMIN] pg_basebackup blocking all queries with horrible performance  (Magnus Hagander <magnus@hagander.net>)
Responses Re: [ADMIN] pg_basebackup blocking all queries with horrible performance  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
On Wed, Jun 20, 2012 at 7:18 AM, Magnus Hagander <magnus@hagander.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


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Pg default's verbosity?
Next
From: Alvaro Herrera
Date:
Subject: Re: Nasty, propagating POLA violation in COPY CSV HEADER