nting read-only queries during wal
replay (SoC 2007)
Paul Silveira wrote:
> Hello,
>
> I just wanted to voice my opinion for this feature... I've implemented a
> few Production applicaitons with PostgreSQL now and would die for that
> feature. Right now, I am constantly try
Paul Silveira wrote:
> Hello,
>
> I just wanted to voice my opinion for this feature... I've implemented a
> few Production applicaitons with PostgreSQL now and would die for that
> feature. Right now, I am constantly trying to find way's to make my data
> more available.
Paul unfortunately yo
Hello,
I just wanted to voice my opinion for this feature... I've implemented a
few Production applicaitons with PostgreSQL now and would die for that
feature. Right now, I am constantly trying to find way's to make my data
more available. I've even resulted to using pg_dump to create read onl
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 "
getting back on topic (ahem), florian: are you comfortable going ahead
with this? is there anything you need help with?
merlin
---(end of broadcast)---
TIP 6: explain analyze is your friend
Jonah H. Harris wrote:
> On 2/26/07, Bruce Momjian <[EMAIL PROTECTED]> wrote:
>> Jonah, I have no idea what "fault" you are trying to blame on the
>> community in the above statement. The author didn't discuss the idea
>> with the community before spending months on it so we have no obligation
>>
On 2/26/07, Bruce Momjian <[EMAIL PROTECTED]> wrote:
Jonah, I have no idea what "fault" you are trying to blame on the
community in the above statement. The author didn't discuss the idea
with the community before spending months on it so we have no obligation
to accept it in the core.
You're
Jonah H. Harris wrote:
> On 2/23/07, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
> > A good example of the wrong way to do it is the Full Disjunctions
> > project. Great idea, Great project, not bitrot and hard space because it
> > hasn't been touched or maintained sense release.
>
> Don't get me s
On 2/24/07, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
Guess we will have to agree to disagree. That is not my recollection of
the events on any level.
Guess so. This topic ended in August and I'm no longer going to argue about it.
--
Jonah H. Harris, Software Architect | phone: 732.331.1324
> He already did over a year and half research on the subject, wrote the
> code for it, published a paper on it, and offered it to the community.
> Why would he choose to spend more time getting beaten up for
> something that's already behind him?
If he is not willing to proceed with public debat
On 2/24/07, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
The argument for not including it was valid, it didn't adhere on several
levels including code style and grammatical changes.
IIRC, the only exception to code style was cleaning up some mixed
code/declaration warnings.
The point is, if th
Jonah H. Harris wrote:
> On 2/23/07, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
>> A good example of the wrong way to do it is the Full Disjunctions
>> project. Great idea, Great project, not bitrot and hard space because it
>> hasn't been touched or maintained sense release.
>
> Don't get me star
On 2/23/07, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
A good example of the wrong way to do it is the Full Disjunctions
project. Great idea, Great project, not bitrot and hard space because it
hasn't been touched or maintained sense release.
Don't get me started there. The decision was split
Tom Lane wrote:
"Florian G. Pflug" <[EMAIL PROTECTED]> writes:
My line of reasoning is that stopping wal replay at a arbitrary point,
and then starting a read-only transaction with an "empty snapshot" (meaning
that all exactly those transactions marked as comitted in the clog are
assumed to be
"Florian G. Pflug" <[EMAIL PROTECTED]> writes:
> My line of reasoning is that stopping wal replay at a arbitrary point,
> and then starting a read-only transaction with an "empty snapshot" (meaning
> that all exactly those transactions marked as comitted in the clog are
> assumed to be visible to
Josh Berkus wrote:
People weren't very interested in having a read-only mode. I think it
would be a nice feature if it's not too complicated.
Actually, I think there's high demand for it off this list. Effectively it
would allow our "warm backup mode" to become a "hot backup mode". As SoC
Heikki Linnakangas wrote:
Florian G. Pflug wrote:
I plan to submit a proposal for implementing support for
read-only queries during wal replay as a "Google Summer of Code 2007"
project.
I've been browsing the postgres source-code for the last few days,
and came up with the following plan for a
On Fri, Feb 23, 2007 at 10:57:24PM +, Heikki Linnakangas wrote:
> Florian G. Pflug wrote:
> >I plan to submit a proposal for implementing support for
> >read-only queries during wal replay as a "Google Summer of Code 2007"
> >project.
> >
> >I've been browsing the postgres source-code for the l
Josh Berkus wrote:
>> People weren't very interested in having a read-only mode. I think it
>> would be a nice feature if it's not too complicated.
>
> Actually, I think there's high demand for it off this list. Effectively it
> would allow our "warm backup mode" to become a "hot backup mode".
> People weren't very interested in having a read-only mode. I think it
> would be a nice feature if it's not too complicated.
Actually, I think there's high demand for it off this list. Effectively it
would allow our "warm backup mode" to become a "hot backup mode". As SoC
admin, I'd vote f
I'll throw in my vote, I would find this quite useful.
-Glen
Florian G. Pflug wrote:
I plan to submit a proposal for implementing support for
read-only queries during wal replay as a "Google Summer of Code 2007"
project.
I've been browsing the postgres source-code for the last few days,
and c
Florian G. Pflug wrote:
I plan to submit a proposal for implementing support for
read-only queries during wal replay as a "Google Summer of Code 2007"
project.
I've been browsing the postgres source-code for the last few days,
and came up with the following plan for a implementation.
I'd be ver
"Florian G. Pflug" <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> You are discussing this on the wrong list.
> So what list would be more appropriate?
My mistake, I read the message header and saw "Postgresql-General" ...
did not look at the actual address ...
regards,
Tom Lane wrote:
"Florian G. Pflug" <[EMAIL PROTECTED]> 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.
So what list would be more appropriate?
B) Split
"Florian G. Pflug" <[EMAIL PROTECTED]> 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
Hi,
Here's some feedback, this is a feature that would be very useful to a
project I am currently working on.
Doug
On Fri, 2007-02-23 at 17:34 +0100, Florian G. Pflug wrote:
> Hi
>
> I plan to submit a proposal for implementing support for
> read-only queries during wal replay as a "Google Summ
26 matches
Mail list logo
