| From: | "Fujii Masao" <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | aidan(at)highrise(dot)ca |
| Cc: | "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>, "Simon Riggs" <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Sync Rep: First Thoughts on Code |
| Date: | 2008-12-12 09:56:25 |
| Message-ID: | 3f0b79eb0812120156j148c0b3ev18079737b68800ca@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Fri, Dec 12, 2008 at 1:34 PM, Aidan Van Dyk <aidan(at)highrise(dot)ca> wrote:
> * Fujii Masao <masao(dot)fujii(at)gmail(dot)com> [081211 23:00]:
>> Hi,
>
>> Or, should I
>> create the feature for the user to confirm whether it's in "synch rep" via SQL?
>
> I don't need a way to check via SQL, but I'ld love a postgresql.conf
> option that when set would make sure that all connections pretty much
> just hang until a slave has connected and everything is setup for "sync
> rep". I think I saw that youre using "normal" connection setup to start
> the wal streaming to the slave, so you have to allow connections, but
> I'ld really not want any of my pg-clients able to do anything if
> sync-rep isn't happenning...
How about stopping the request / connection from a client in front of
postgres (e.g. connection pooling software)? Or, we should develop
the feature like OFFLINE of Oracle apart from Synch Rep at first.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2008-12-12 11:35:07 | Re: Sync Rep: First Thoughts on Code |
| Previous Message | ITAGAKI Takahiro | 2008-12-12 09:51:38 | contrib/pg_stat_statements 1212 |