Re: [Solved] Corrupt indexes on slave when using pg_bulkload on master - Mailing list pgsql-general

From Fujii Masao
Subject Re: [Solved] Corrupt indexes on slave when using pg_bulkload on master
Date
Msg-id CAHGQGwFq90gqPbVwOzJ_-E6-xyqFb4Z1OQ58Oz7dFPYezxqEog@mail.gmail.com
Whole thread Raw
In response to Re: [Solved] Corrupt indexes on slave when using pg_bulkload on master  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [Solved] Corrupt indexes on slave when using pg_bulkload on master  ("Takashi Ohnishi" <onishi_takashi_d5@lab.ntt.co.jp>)
List pgsql-general
On Thu, Jan 10, 2013 at 6:51 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> James Cowell <jcowell@btinternet.com> writes:
>> But pg_bulkload only puts the index updates into WAL if you also have
>>
>> archive_mode = on
>>
>> I guess it needs to test wal_level rather than archive mode now?  It looks like changes to the project have been
minimalfor some time, which is a shame because it's a very useful tool. 
>
> Oh, the code in question is in pg_bulkload not the backend?  Yeah, it
> sounds like it hasn't tracked some core-code changes.  In particular
> you might point the author at
> http://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=40f908bdcdc726fc11912cd95dfd2f89603d1f37#patch10
> which shows how it needs to be done in 9.0 and later.

I reported this problem to the author in offlist. Thanks for the bug report!

Regards,

--
Fujii Masao


pgsql-general by date:

Previous
From: Peter Kroon
Date:
Subject: Identifier gets truncated
Next
From: Lonni J Friedman
Date:
Subject: data corruption when using base backups generated from hot standby