Re: Index corruption

Thanks for the input.

We'll upgrade to 9.2.10 and attempt to reproduce the issue.

If possible, can someone point to corruption related issues fixed after
9.2.0?

Thanks,
-Bankim.

On 03/24/2015 11:56 AM, David G. Johnston wrote:
> On Tuesday, March 24, 2015, Bankim Bhavsar <bankim(at)nimblestorage(dot)com
> <mailto:bankim(at)nimblestorage(dot)com>> wrote:
>
> Hello postgres experts,
>
> We are running a test that periodically abruptly kills postgres
> process(equivalent to kill -9) and restarts it.
> After running this test for 24 hrs or so, we see duplicate primary
> key entries in postgres table.
>
> We detect this as we load internal hash-table data-structure in a
> separate process with primary key entries.
>
> Before hitting this issue we see following warning messages in pg_log
>
> 17365 2015-03-24 03:01:42.729 GMTWARNING: page is not marked
> all-visible but visibility map bit is set in relation "table_foo"
> page 12
> 17365 2015-03-24 03:01:42.729 GMTWARNING: page is not marked
> all-visible but visibility map bit is set in relation "table_foo"
> page 13
>
>
> Some information about postgres setup.
> - 9.2.0
> - We use standard configuration with shared_buffer setting as 32MB
> and checkpoint_timeout as 1 min.
> - In this particular case postgres replication is not enabled.
>
> Let me know if more information is needed to help understand this
> issue.
>
> Any help or pointers will be appreciated.
>
>
> If you really are running 9.2.0 instead of 9.2.10 you should upgrade
> and reconfirm.
>
> David J.