| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | James Cowell <jcowell(at)btinternet(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, "wd(at)wdicc(dot)com" <wd(at)wdicc(dot)com> |
| Subject: | Re: [Solved] Corrupt indexes on slave when using pg_bulkload on master |
| Date: | 2013-01-08 18:02:08 |
| Message-ID: | 11170.1357668128@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
James Cowell <jcowell(at)btinternet(dot)com> writes:
> I enabled archive mode (which I didn't care about before as the database only holds 36 hours of data) and the indexes seem to replicate over fine. I suppose the problem here is lack of documentation, but at least the code is well commented :)
> It looks like pg_bulkload works just fine with replication so long as it's set up right.
Hm. I had thought we had interlocks in there to prevent turning on
replication unless the WAL level was sufficiently high. It sounds like
you managed to dodge that sanity check. Could you be more specific about
what your replication configuration looks like?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fuhry | 2013-01-08 18:11:25 | Re: pgxs "missing magic block ... PG_MODULE_MAGIC" with "MODULE_big" |
| Previous Message | Tom Lane | 2013-01-08 17:55:47 | Re: pgxs "missing magic block ... PG_MODULE_MAGIC" with "MODULE_big" |