From: | Yan Chunlu <springrider(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Tomas Vondra <tv(at)fuzzy(dot)cz>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org, Martin Pitt <mpitt(at)debian(dot)org> |
Subject: | Re: streaming replication does not work across datacenter with 20ms latency? |
Date: | 2011-07-25 16:17:42 |
Message-ID: | CAOA66tH=bWQN5xOOkDB3dKMDAOup9NOO_9vK5=-_ub-uDfaoyA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
how about 4.3.2?
I have gcc 4.3.2 compiled postgresql 9.0.4 as slave, is that okay
that I turn the slave into master? so the switch will be a lot more
smooth.
On Tue, Jul 26, 2011 at 12:08 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Yan Chunlu <springrider(at)gmail(dot)com> writes:
>> oh god...thanks a lot for the tip. I did actually lost some data, the
>> master server has crashed two times. every time it comes back, the
>> index were broken. I need to reindex it. I have already set fsync=on.
>> just thought it was normal behavior....
>
> Uh, no.
>
>> about gcc version, only 4.6.0 effected? 4.6.1 is okay? then I could
>> compile my own version with 4.6.1
>
> It's supposed to be fixed in 4.6.1 according to
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49390
>
> Personally I'd use 4.6.1 *and* apply the Postgres patch.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Markus Wollny | 2011-07-25 16:27:23 | Re: Query, usually running <300ms, sometimes hangs for hours |
Previous Message | Tom Lane | 2011-07-25 16:08:15 | Re: streaming replication does not work across datacenter with 20ms latency? |