| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: HS/SR and smart shutdown |
| Date: | 2010-01-29 19:43:06 |
| Message-ID: | 4B633A4A.1000404@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Fujii,
> I guess that the startup process and the walreceiver should wait
> for all read only backends to exit in smart shutdown case. It's
> because those backends might be waiting for the record that conflicts
> with their queries to be replayed. Is this OK? Or we should kill the
> startup process and the walreceiver on ahead?
>
> If my guess is right, we would need to add new PMState to cancel
> recovery and replication after all read only connections have died.
How could existing read queries on the slave be waiting on a WAL record?
I don't follow this.
--Josh Berkus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2010-01-29 19:44:28 | Re: Hot Standby: Relation-specific deferred conflict resolution |
| Previous Message | Josh Berkus | 2010-01-29 19:41:38 | Re: Hot Standby: Relation-specific deferred conflict resolution |