| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Florian G(dot) Pflug" <fgp(at)phlo(dot)org> |
| Cc: | Postgresql-General <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal for Implenting read-only queries during wal replay (SoC 2007) |
| Date: | 2007-02-23 17:00:51 |
| Message-ID: | 912.1172250051@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Florian G. Pflug" <fgp(at)phlo(dot)org> writes:
> I plan to submit a proposal for implementing support for
> read-only queries during wal replay as a "Google Summer of Code 2007"
> project.
You are discussing this on the wrong list.
> B) Split StartupXLOG into two steps. The first (Recovery) will process
> only enough wal to bring the system into a consistent state,
How will you know what that is?
> C) Combine A) and B), in the simplest possible way.
> Introduce a global R/W lock, which is taken by the Replay part
> of B) in write mode before replaying a chunk, then released,
> and immediatly reaquired before replaying the next chunk.
That seems certain to result in intolerable performance, for both the
queries and the replay process.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2007-02-23 17:21:21 | Re: autovacuum next steps, take 2 |
| Previous Message | Doug Knight | 2007-02-23 16:56:41 | Re: Proposal for Implenting read-only queries during wal replay (SoC 2007) |