From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ray Stell <stellr@vt.edu>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: 9.0.15 WAL mis-replay status?
Date: Mon, 28 Apr 2014 16:25:00 -0400
Message-ID: <26635.1398716700@sss.pgh.pa.us> (raw)
In-Reply-To: <5484E2AE-F298-470B-9412-05D9EEFEAE7F@vt.edu>
References: <8D8B1117-25D3-4C82-9FB5-6CE5C8E2C3EC@vt.edu>
<12664.1398697642@sss.pgh.pa.us>
<5484E2AE-F298-470B-9412-05D9EEFEAE7F@vt.edu>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Ray Stell <stellr@vt.edu> writes:
> On Apr 28, 2014, at 11:07 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Note however that the issue could only arise on tables that exceed 1GB
> I assume this is true also for other relkinds? I have >1G indexes here, but tables are <1G. TIA.
Right, such indexes would be at risk. However, if it's only the indexes
that exceed 1G, you could consider reindexing those indexes as an
alternative to a full resync.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, stellr@vt.edu
Subject: Re: 9.0.15 WAL mis-replay status?
In-Reply-To: <26635.1398716700@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox