| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | josh(at)agliodbs(dot)com, pgsql-hackers(at)postgresql(dot)org, Bruce Momjian <bruce(at)momjian(dot)us> |
| Subject: | Re: Standby Mode |
| Date: | 2006-08-03 06:01:00 |
| Message-ID: | 1154584860.2495.4.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2006-08-02 at 18:49 -0400, Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> > [I have an outstanding question on how to include LWlock support into
> > the archiver, required to flesh out the feature set, and of course
> > assuming these patches being accepted.]
>
> The archiver is deliberately designed not to be connected to shared
> memory. If you want to change that you'll have to make a very strong
> case why we should give up the safety and security advantages of it.
We should let the user decide.
If archiver_timeout is a server start GUC then we can attach to shared
memory if it is set, if not we avoid that.
If they are in a position to want that functionality they can make that
trade-off.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2006-08-03 10:53:04 | Re: [HACKERS] 8.2 feature set |
| Previous Message | Jaime Casanova | 2006-08-03 05:58:52 | Re: [HACKERS] Rebuilding DB from broken hardrive. |