Re: Proposal for Implenting read-only queries during wal replay (SoC 2007) - Mailing list pgsql-hackers

From Florian G. Pflug
Subject Re: Proposal for Implenting read-only queries during wal replay (SoC 2007)
Date
Msg-id 45E43BF9.1070404@phlo.org
Whole thread Raw
In response to Re: Proposal for Implenting read-only queries during wal replay (SoC 2007)  ("Merlin Moncure" <mmoncure@gmail.com>)
List pgsql-hackers
Merlin Moncure wrote:
> getting back on topic (ahem), florian: are you comfortable going ahead
> with this?  is there anything you need help with?

I'm currently updating my proposal, trying to incorporate the points
people brought up in this thread.

I realized that trying to use the same kind of "read only mode" for
both a standalone postgres (with the datadir on read-only storage),
and a PITR-slave was missguided - 
http://archives.postgresql.org/pgsql-hackers/2005-11/msg01043.php
was really enlightning ;-)

Tom's objects regarding performance are the hardest one to deal with -
I'm currently thinking about ways that the locking requirements could
be relaxed - though I still plan to do a basic implementation first, and 
then try to improve it.

I'll post an updated proposal during the next few days.

greetings, Florian Pflug


pgsql-hackers by date:

Previous
From: "Florian G. Pflug"
Date:
Subject: Re: Expanding DELETE/UPDATE returning
Next
From: "Chad Wagner"
Date:
Subject: Re: Developer TODO List as a PostgreSQL DB