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
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
