On Wed, Jun 8, 2011 at 3:59 AM, A J wrote:
> Ok. So if I understand it correctly, as far as Postgres is concerned the
> 'mirror is broken'. It is a one-time cutover.
> We then rely on filesystem tools (or other third party tools) to get the
> original master in sync with the new master efficiently
Simon Riggs writes:
> On Tue, Jun 7, 2011 at 8:41 PM, Ray Stell wrote:
>
>> On Tue, Jun 07, 2011 at 11:59:07AM -0700, A J wrote:
>>> We then rely on filesystem tools (or other third party tools) to get the
>>> original master in sync with the new master efficiently and then make it
>>> join as
On Tue, Jun 7, 2011 at 10:33 PM, A J wrote:
> Having a master and 2 slaves in synchronous replication mode in 9.1
> The master seems to wait for only one slave to respond before considering
> the transaction to be complete. I have done the setting for master to wait
> for all the slaves to finish
Hello
Having a master and 2 slaves in synchronous replication mode in 9.1
The master seems to wait for only one slave to respond before considering the
transaction to be complete. I have done the setting for master to wait for all
the slaves to finish:
synchronous_standby_names = '*'
I even tri
On Tue, Jun 7, 2011 at 8:41 PM, Ray Stell wrote:
> On Tue, Jun 07, 2011 at 11:59:07AM -0700, A J wrote:
>> We then rely on filesystem tools (or other third party tools) to get the
>> original master in sync with the new master efficiently and then make it
>> join as
>> slave.
>
> the doc would no
On Tue, Jun 07, 2011 at 11:59:07AM -0700, A J wrote:
> We then rely on filesystem tools (or other third party tools) to get the
> original master in sync with the new master efficiently and then make it join
> as
> slave.
the doc would not be corrupted by an additional few words that stated as
A J wrote:
> Ok. So if I understand it correctly, as far as Postgres is
> concerned the 'mirror is broken'. It is a one-time cutover.
> We then rely on filesystem tools (or other third party tools) to
> get the original master in sync with the new master efficiently
> and then make it join as sl
Ok. So if I understand it correctly, as far as Postgres is concerned the
'mirror
is broken'. It is a one-time cutover.
We then rely on filesystem tools (or other third party tools) to get the
original master in sync with the new master efficiently and then make it join
as
slave.
Right ?
___
A J wrote:
> What does it exactly mean to 'recreate a standby server' ? Can I
> not use the datafiles on the former primary and just let it sync
> and get the incremental from the new primary ? Do I have to remove
> all the data files from the former primary and get all the
> datafiles through r
On Tue, 2011-06-07 at 11:33 -0700, A J wrote:
> >>To return to normal operation, a standby server must be recreated,
> either on the former primary system when it comes up<<
>
>
> What does it exactly mean to 'recreate a standby server' ? Can I not
> use the datafiles on the former primary and ju
>>To return to normal operation, a standby server must be recreated, either on
>>the
>>former primary system when it comes up<<
What does it exactly mean to 'recreate a standby server' ? Can I not use the
datafiles on the former primary and just let it sync and get the incremental
from the new
On Tue, Jun 07, 2011 at 09:32:31AM -0700, A J wrote:
> Hello,
> I am trying to switch the master and slave roles in a test I am doing with
> streaming replication in 9.1 beta.
>
http://www.postgresql.org/docs/9.1/static/warm-standby-failover.html
Once failover to the standby occurs, there is on
Did you configure a system DSN or user DSN? If connections fail for postgres
and succeed for other users, then look in the postgres user's home for hidden
file ~/.odbc.ini. Each user can have one of these hidden files.
-Mark
-Original Message-
From: 최재원 [mailto:jwc...@modernlimes.com]
Sen
Hello,
I am trying to switch the master and slave roles in a test I am doing with
streaming replication in 9.1 beta.
To start with, I have one master (N1 node) and one slave (N2 node).
I stop N1 and promote N2 as primary (by touching the trigger file).
Now I wish for N1 to come back up as slave
Hi,
I was checked and checked my Odbc.ini File.
I tried connection unixODBC(isql) to oracle with “root” user in linux OS.
I got TNS permission problem.
So, I tried connection unixODBC(isql) to oracle with “oracle” user in
linux OS.
Then connected.
And I tried connection postgresql
15 matches
Mail list logo
