| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. |
| Date: | 2011-03-07 09:30:35 |
| Message-ID: | 1299490235.1696.7973.camel@ebony |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Mon, 2011-03-07 at 17:44 +0900, Fujii Masao wrote:
> The above check should be required also after pg_ctl reload since
> synchronous_standby_names can be changed by SIGHUP?
> Or how about just removing that? If the patch I submitted is
> committed,empty synchronous_standby_names and max_wal_senders = 0
> settings is no longer unsafe.
Ah, on reload. I plugged the gap only at startup.
I'll fix by changing assign_synchronous_standby_names(), not by changing
lots of other parts of code and making runtime check each COMMIT.
--
Simon Riggs http://www.2ndQuadrant.com/books/
PostgreSQL Development, 24x7 Support, Training and Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2011-03-07 09:47:20 | Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. |
| Previous Message | Fujii Masao | 2011-03-07 09:28:25 | Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2011-03-07 09:31:22 | Re: Composite Index Structure |
| Previous Message | Fujii Masao | 2011-03-07 09:28:25 | Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. |