Torsten Förtsch wrote:
> That's what I want, to throttle the rate at which WAL is generated by
> maintenance operations.
>
> I take it, there is no such thing by now. Would it be a useful addition?
Uh. See this thread:
http://www.postgresql.org/message-id/ca+u5nmlfxbghq1vlsebhyemjhxz_ohskufdu6_
On 5/22/2014 12:31 PM, Torsten Förtsch wrote:
That's what I want, to throttle the rate at which WAL is generated by
maintenance operations.
I take it, there is no such thing by now. Would it be a useful addition?
I am not sure if I have the time to implement it. I have had a cursory
look at the
On 22/05/14 21:05, Jeff Janes wrote:
> time and again I need to build indexes. If they are big, that
> generates
> a lot of WAL data that needs to be replicated to streaming
> replication
> slaves. Usually these slaves don't lag behind noticeably. So, the
>
On 05/22/2014 12:04 PM, John R Pierce wrote:
On 5/22/2014 11:46 AM, Joshua D. Drake wrote:
This does not appear the domain of PostgreSQL as much as the domain of
your OS and network layer.
I think he's asking for a throttle on create index, so OTHER WAL
activity would proceed at full speed,
On Thu, May 22, 2014 at 11:46 AM, Joshua D. Drake wrote:
>
> On 05/22/2014 11:25 AM, Torsten Förtsch wrote:
>
>>
>> Hi,
>>
>> time and again I need to build indexes. If they are big, that generates
>> a lot of WAL data that needs to be replicated to streaming replication
>> slaves. Usually these s
On 5/22/2014 11:46 AM, Joshua D. Drake wrote:
This does not appear the domain of PostgreSQL as much as the domain of
your OS and network layer.
I think he's asking for a throttle on create index, so OTHER WAL
activity would proceed at full speed, but the CREATE INDEX would somehow
constrain
On 05/22/2014 11:25 AM, Torsten Förtsch wrote:
Hi,
time and again I need to build indexes. If they are big, that generates
a lot of WAL data that needs to be replicated to streaming replication
slaves. Usually these slaves don't lag behind noticeably. So, the
application often reads from them.
Hi,
time and again I need to build indexes. If they are big, that generates
a lot of WAL data that needs to be replicated to streaming replication
slaves. Usually these slaves don't lag behind noticeably. So, the
application often reads from them. Well, unless I build indexes and,
thus, create a h
