Re: wal-size limited to 16MB - Performance issue for subsequent backup

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: <jesper(at)krogh(dot)cc>, Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: wal-size limited to 16MB - Performance issue for subsequent backup
Date: 2014-10-22 06:56:02
Message-ID: 54475502.8030505@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10/20/2014 11:02 PM, jesper(at)krogh(dot)cc wrote:
>>> >>I do suspect the majority is from 30 concurrent processes updating an
>>> >>506GB GIN index, but it would be nice to confirm that. There is also a
>>> >>message-queue in the DB with a fairly high turnaround.
>> >
>> >A 506GB GIN index? Uh, interesting :). What's it used for? Trigrams?
> It is for full-text-search, but it is being updated entirely regulary,
> ~100M records. A dump/restore cycle typically reduces the size to 30-40%
> of current size.

Try 9.4 beta. The on-disk format of GIN indexes was rewritten in 9.4,
making them a lot smaller. That might help with WAL volume too. Or not,
but I'd love to hear what the impact is, in a real-life database :-).

- Heikki

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andreas Karlsson 2014-10-22 07:06:52 Reducing lock strength of adding foreign keys
Previous Message edward745 2014-10-22 06:14:29 Re: Getting rid of "accept incoming network connections" prompts on OS X