Re: tracking commit timestamps
| От | Simon Riggs |
|---|---|
| Тема | Re: tracking commit timestamps |
| Дата | |
| Msg-id | CA+U5nMJcJz11DpZyZ0okc6Ru8G6YDK_5HPqRfHOvjdRY2eJbAg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: tracking commit timestamps (Fujii Masao <masao.fujii@gmail.com>) |
| Ответы |
Re: tracking commit timestamps
|
| Список | pgsql-hackers |
On 4 December 2014 at 03:08, Fujii Masao <masao.fujii@gmail.com> wrote:
> #1. set up and start the master and standby servers with
> track_commit_timestamp disabled
> #2. enable track_commit_timestamp in the master and restart the master
> #3. run some write transactions
> #4. enable track_commit_timestamp in the standby and restart the standby
> #5. execute "select pg_xact_commit_timestamp('1000'::xid)" in the standby
I'm not sure what step4 is supposed to do?
Surely if steps 1-3 generate any WAL then the standby should replay
it, whether or not track_commit_timestamp is enabled.
So what effect does setting that parameter on the standby?
-- Simon Riggs http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: