Re: [HACKERS] [DOCS] max_worker_processes on the standby

2015-12-03 Thread Petr Jelinek
ook this over I would appreciate it. While this seems good, I'd code it slightly differently. I didn't like the addition of new bool when it's not really needed. This brings the question if we actually need the BootStrapCommitTs and StartupCommitTs functions which really don't

Re: [HACKERS] [DOCS] max_worker_processes on the standby

2015-10-17 Thread Petr Jelinek
y I also removed no longer used do_wal parameters in couple of functions. -- Petr Jelinek http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services diff --git a/src/backend/access/transam/commit_ts.c b/src/backend/access/transam/commit_ts.c index 24

Re: [DOCS] max_worker_processes on the standby

2015-09-15 Thread Petr Jelinek
s. It just removes the on start check for track_commit_timestamp being same in config and control file. -- Petr Jelinek http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services From 49533f556d8120564ed81dc67acfcc03d2894166 Mon Sep 17 00:00:00 2

Re: [DOCS] max_worker_processes on the standby

2015-08-05 Thread Petr Jelinek
rack_commit_timestamps is off in config because the the SQL interface will complain if called on the slave So +0.5 from me towards following master and removing the error message -- Petr Jelinek http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Ser