Just turned on WAL archiving to an S3 bucket for a small database - total size
of perhaps 2-4G. After turning on achiving, we're seeing WAL logs written to
S3 at the rate of about 1G every 3 minutes. That seems completely unreasonable
given usage of the db. I can even see that nearly nothing
On Wed, Jun 19, 2013 at 4:22 PM, Sean Dillon wrote:
> Just turned on WAL archiving to an S3 bucket for a small database - total
> size of perhaps 2-4G. After turning on achiving, we're seeing WAL logs
> written to S3 at the rate of about 1G every 3 minutes. That seems
> completely unreasonable g
bricklen wrote:
> On Wed, Jun 19, 2013 at 4:22 PM, Sean Dillon wrote:
>> Just turned on WAL archiving to an S3 bucket for a small database - total
>> size of perhaps 2-4G.
>> After turning on achiving, we're seeing WAL logs written to S3 at the rate
>> of about 1G every 3
>> minutes. That seems
