From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | James Cowell <jcowell(at)btinternet(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: [Solved] Corrupt indexes on slave when using pg_bulkload on master |
Date: | 2013-01-10 14:50:31 |
Message-ID: | CAHGQGwFq90gqPbVwOzJ_-E6-xyqFb4Z1OQ58Oz7dFPYezxqEog@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Jan 10, 2013 at 6:51 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> James Cowell <jcowell(at)btinternet(dot)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 minimal for 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
From | Date | Subject | |
---|---|---|---|
Next Message | wschwurack | 2013-01-10 15:02:01 | Re: Error: absolute path not allowed |
Previous Message | Peter Kroon | 2013-01-10 14:36:32 | Identifier gets truncated |