Sponsored Content
Top Forums Web Development MySQL Master-Slave Configuration: Don't Replicate a Row of a Table? Post 302461259 by radoulov on Saturday 9th of October 2010 01:56:17 PM
Old 10-09-2010
This is from the documentation of 5.0 (and I believe it's valid for 5.1 as well):

Quote:
23.5.9: Do triggers work with replication? Triggers and replication in MySQL 5.0 work in the same way as in most other database systems: Actions carried out through triggers on a master are not replicated to a slave server. Instead, triggers that exist on tables that reside on a MySQL master server need to be created on the corresponding tables on any MySQL slave servers so that the triggers activate on the slaves as well as the master.
For more information, see Section 16.4.1.25, “Replication and Triggers”.
Replication and triggers should work as expected, I'm not sure if updating the same rows via statement and triggers on the same table (and at the same time) works though ...
 

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

NIS master / slave problems

Our NIS master server went down. We have since fixed it and brought it back up. However all of are machines still point to the slave server when looking at it with ypwhich. My question is how do i point the servers back to the master. Frank (2 Replies)
Discussion started by: frankkahle
2 Replies

2. SCO

master and slave in lan network

hello , i setup a lan network , but i don't know how configure master and slave in the lan network please help me:confused: (2 Replies)
Discussion started by: hossein
2 Replies

3. AIX

Slave NIS server configuration change

Hello Everybody, I have a question regarding SLAVE NIS SERVER in aix. We are using NIS master of Sun Solaris 9.0 which is on different subnet i.e. 10.197.93.0. And Our slave server is having AIX 5.3 installed which is on 10.207.13.0 subnet. I have a query regarding its name and ip address... (0 Replies)
Discussion started by: jit15975
0 Replies

4. Shell Programming and Scripting

mysql how to select a specific row from a table

i have a table records ------------ id | user | time | event 91 admin | 12:00 | hi 92 admin | 11:00 | hi 93 admin | 12:00 | bye 94 admin | 13:00 | bye 95 root | 12:00 | hi 96 root | 12:30 | hi 97 root | 12:56 | hi how could i only select and display only the user and event from... (6 Replies)
Discussion started by: kpddong
6 Replies

5. Programming

Asynchronous communication between master and slave threads

I am writing a process that has a master thread and a set of slave threads. Master thread is supposed to get jobs dynamically and assign to slave thread which is free. Master also get results back from slaves once a job is done. The number of slaves should be adjustable dynamically based on job... (1 Reply)
Discussion started by: tamil.pamaran
1 Replies

6. UNIX Desktop Questions & Answers

How can I replicate master master and master master MySQL databse replication and HA?

I have an application desigend in PHP and MySQl running on apache web server that I is running on a Amazon EC2 server Centos. I want to implement the master-master and master slave replication and high availability disaster recovery on this application database. For this I have created two... (0 Replies)
Discussion started by: Palak Sharma
0 Replies

7. Programming

How to wait the slave to be finished first then execute the master--MPI C++?

Hi, How to wait the slave to be finished first then execute the master? Can someone give me the specific function? Or the detailed example. Thanks~ (1 Reply)
Discussion started by: wanliushao
1 Replies

8. IP Networking

DNS question about initial Master/Slave setup

Hey everyone. I'm creating a DNS master/slave server set up. I have the configurations all done I believe, the master has the required zone file, and the named.conf file has the allow transfer and allow query stuff set. The slave has it's own configs set. My question is that when initially... (1 Reply)
Discussion started by: Lost in Cyberia
1 Replies
OCF_HEARTBEAT_PGSQL(7)						OCF resource agents					    OCF_HEARTBEAT_PGSQL(7)

NAME
ocf_heartbeat_pgsql - Manages a PostgreSQL database instance SYNOPSIS
pgsql [start | stop | status | monitor | promote | demote | meta-data | validate-all] DESCRIPTION
Resource script for PostgreSQL. It manages a PostgreSQL as an HA resource. SUPPORTED PARAMETERS
pgctl Path to pg_ctl command. (optional, string, default "/usr/bin/pg_ctl") start_opt Start options (-o start_opt in pg_ctl). "-i -p 5432" for example. (optional, string, no default) ctl_opt Additional pg_ctl options (-w, -W etc..). (optional, string, no default) psql Path to psql command. (optional, string, default "/usr/bin/psql") pgdata Path to PostgreSQL data directory. (optional, string, default "/var/lib/pgsql/data") pgdba User that owns PostgreSQL. (optional, string, default "postgres") pghost Hostname/IP address where PostgreSQL is listening (optional, string, no default) pgport Port where PostgreSQL is listening (optional, integer, default 5432) monitor_user PostgreSQL user that pgsql RA will user for monitor operations. If it's not set pgdba user will be used. (optional, string, no default) monitor_password Password for monitor user. (optional, string, no default) monitor_sql SQL script that will be used for monitor operations. (optional, string, default "select now();") config Path to the PostgreSQL configuration file for the instance. (optional, string, default "/var/lib/pgsql/data/postgresql.conf") pgdb Database that will be used for monitoring. (optional, string, default "template1") logfile Path to PostgreSQL server log output file. (optional, string, default "/dev/null") socketdir Unix socket directory for PostgreSQL (optional, string, no default) stop_escalate Number of shutdown retries (using -m fast) before resorting to -m immediate (optional, integer, default 30) rep_mode Replication mode may be set to "async" or "sync" or "slave". They require PostgreSQL 9.1 or later. Once set, "async" and "sync" require node_list, master_ip, and restore_command parameters,as well as configuring PostgreSQL for replication (in postgresql.conf and pg_hba.conf). "slave" means that RA only makes recovery.conf before starting to connect to primary which is running somewhere. It dosen't need master/slave setting. It requires master_ip restore_command parameters. (optional, string, default "none") node_list All node names. Please separate each node name with a space. This is required for replication. (optional, string, no default) restore_command restore_command for recovery.conf. This is required for replication. (optional, string, no default) archive_cleanup_command archive_cleanup_command for recovery.conf. This is used for replication and is optional. (optional, string, no default) recovery_end_command recovery_end_command for recovery.conf. This is used for replication and is optional. (optional, string, no default) master_ip Master's floating IP address to be connected from hot standby. This parameter is used for "primary_conninfo" in recovery.conf. This is required for replication. (optional, string, no default) repuser User used to connect to the master server. This parameter is used for "primary_conninfo" in recovery.conf. This is required for replication. (optional, string, default "postgres") primary_conninfo_opt primary_conninfo options of recovery.conf except host, port, user and application_name. This is optional for replication. (optional, string, no default) restart_on_promote If this is true, RA deletes recovery.conf and restarts PostgreSQL on promote to keep Timeline ID. It probably makes fail-over slower. It's recommended to set on-fail of promote up as fence. This is optional for replication. (optional, boolean, default false) tmpdir Path to temporary directory. This is optional for replication. (optional, string, default "/var/lib/pgsql/tmp") xlog_check_count Number of checks of xlog on monitor before promote. This is optional for replication. (optional, integer, no default) crm_attr_timeout The timeout of crm_attribute forever update command. Default value is 5 seconds. This is optional for replication. (optional, integer, default 5) stop_escalate_in_slave Number of shutdown retries (using -m fast) before resorting to -m immediate in slave state. This is optional for replication. (optional, integer, default 30) check_wal_receiver If this is true, RA checks wal_receiver process on monitor and notifies its status using "(resource name)-receiver-status" attribute. It's useful for checking whether PostgreSQL (hot standby) connects to primary. The attribute shows status as "normal" or "ERROR". (optional, boolean, default false) SUPPORTED ACTIONS
This resource agent supports the following actions (operations): start Starts the resource. Suggested minimum timeout: 120. stop Stops the resource. Suggested minimum timeout: 120. status Performs a status check. Suggested minimum timeout: 60. monitor Performs a detailed status check. Suggested minimum timeout: 30. Suggested interval: 30. monitor (Master role) Performs a detailed status check. Suggested minimum timeout: 30. Suggested interval: 29. promote Promotes the resource to the Master role. Suggested minimum timeout: 120. demote Demotes the resource to the Slave role. Suggested minimum timeout: 120. notify Suggested minimum timeout: 90. meta-data Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5. validate-all Performs a validation of the resource configuration. Suggested minimum timeout: 5. methods Suggested minimum timeout: 5. EXAMPLE
The following is an example configuration for a pgsql resource using the crm(8) shell: primitive p_pgsql ocf:heartbeat:pgsql op monitor depth="0" timeout="30" interval="30" op monitor depth="0" timeout="30" interval="29" role="Master" ms ms_pgsql p_pgsql meta notify="true" interleave="true" SEE ALSO
http://www.linux-ha.org/wiki/pgsql_(resource_agent) AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors) resource-agents UNKNOWN 06/09/2014 OCF_HEARTBEAT_PGSQL(7)
All times are GMT -4. The time now is 10:59 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy