[pgsql-jp: 35237] Re: pgpoolとTRIGGER

[荒井 哲三]

石井様、

平素よりお世話になっております。荒井です。
返信有難うございます。

片方のタイムロケールがJSTで片方がCDTであることがわかりました。
これって関係しますでしょうか？

申しわけありません。-d出力はしていなかったもので。。。
以下confの設定内容です。
#
# pgpool configuration file sample
# $Header: /cvsroot/pgpool/pgpool/pgpool.conf.sample,v 1.1.1.1 2005/02/14 14:52:21 t-ishii Exp $

# host name or IP address to listen on: '*' for all, '' for no TCP/IP connections
listen_addresses = '*'

# port number for pgpool
port = 9999

# Unix domain socket path. Debian package default to /var/run/postgresql!
socket_dir = '/tmp'

# host name where PostgreSQL server is running on. '' means localhost using UNIX
# domain socket
backend_host_name = '192.168.2.30'

# port number PostgreSQL server is running on.
backend_port = 5432

# Unix domain socket path for the backend. Debian package default to /var/run/postgresql!
backend_socket_dir = '/tmp'

# host name where secondary PostgreSQL server is running on. '' means localhost using UNIX
# domain socket
secondary_backend_host_name = '192.168.2.31'

# port number secondary PostgreSQL server is running on.
# 0 means no secondrary PostgreSQL
secondary_backend_port = 5432

# number of pre-forked child process
num_init_children = 32

# numer of connection pool allowed for a child process.
max_pool = 8

# if idle for this seconds, child exits. 0 means no timeout.
child_life_time = 300

# if idle for this seconds, connection to PostgreSQL closes. 0 means
# no timeout
connection_life_time = 0

# logging directory
logdir = '/tmp'

# replication mode
replication_mode = true

# set this to true if you want to avoid deadlock situation when
# replication enabled.
# there will be noticable performance degration, however.
# a work around is set this to false and insert /*STRICT*/ comment
# at the beginning of the SQL command.
replication_strict = true

# when replication_strict is set to false, there will be a chance for
# deadlocks. set this to non 0 (in milli seconds) to detect this
# situation and resolve the deadlock aborting current session.
replication_timeout = 5000

# load balancing mode. i.e. all SELECT except in a transaction block
# are load balanced. This is ignored if replication_mode is false.
load_balance_mode = true

# load balance weight for master and secondary. actual weight is
# calculated by weight_master:weight_secondary. For example both
#
# weight_master = 10 and weight_secondary = 5
# weight_master = 4 and weight_secondary = 2
#
# are regarded as master has double the weight comparing with secondary.
# master and secondary have same weight in the default.
weight_master = 0.5
weight_secondary = 0.5

# if there's a data mismatch between master and secondary
# start degenration to stop replication mode
replication_stop_on_mismatch = true

# semicolon separated list of quries to be issued at the end of session
reset_query_list = 'ABORT; RESET ALL; SET SESSION AUTHORIZATION DEFAULT'

# if true print time stamp to each log line
print_timestamp = true

# if true, operate in master/slave mode
master_slave_mode = false

# if true, cache connection pool
connection_cache = true

# health check timeout. 0 means no timeout;
health_check_timeout = 20

# health check period. 0 means no health check
health_check_period = 0

# health check user
health_check_user = 'nobody'

荒井

On Mon, 11 Apr 2005 12:56:33 +0900 (JST)
Tatsuo Ishii <t-ishii ＠ sra.co.jp> wrote:

> 石井です．
> 
> > 現在、redhat AS 3.0にてpostgres7.4.7を使用しています。
> > pgpoolを使用して、2台のpostgresを使用していますが、
> > 縮退運転に入ってしまいました。
> > 
> > システムにて、TRIGGERを使用して、あるテーブルが更新されると、
> > あるテーブルが更新する仕組みになっております。
> > 
> > pgpoolを使用する場合には、TRIGGERを使用するシステムは、
> > 不向きなのでしょうか？
> 
> これだけでは状況がわからないので，pgpool -dでの出力と，pgpool.confを見
> せてもらえませんか？
> --
> Tatsuo Ishii