Hi all,
Given a cluster of three database servers running 9.1.3 (master, sync
slave, async slave), it seems that there are two ways to promote the sync
slave to become master:
1. pg_ctl promote the sync slave (increments timeline counter)
2. remove recovery.conf on the sync slave and pg_ctl rest
I have configured a two-node 9.1 cluster with synchronous streaming
replication. In the event that the standby server fails, a daemon will
degrade the cluster by setting synchronous_standby_names to "" on the
master and reload the config. (My use case is such where availability is
preferred over
I have a large, frequently accessed table that needs a primary key
constraint added. The table already has a unique index (but not a unique
constraint) on one of its columns. The overly simplified schema looks like
this:
CREATE TABLE table_without_pk (not_a_pk integer not null, some_data text);
subscribe
i was suppose to read the news group, not to receive messages
in my mail box, which is what happens since few days
can anyone in charge see what happens: it's only sort of 2 days
ago that this started, before everything was OK
thanks,
david
---(end of broadcast)-