Zdenek Kotala wrote:
Heikki Linnakangas wrote:
- heap page diagnostic functions
I would like to take this review (after PGCon).
Too late, Bruce applied it already :).
More eyeballs on it still wouldn't hurt of course.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
Heikki Linnakangas wrote:
- heap page diagnostic functions
I would like to take this review (after PGCon).
Zdenek
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
Heikki Linnakangas wrote:
Zdenek Kotala wrote:
Heikki Linnakangas wrote:
- heap page diagnostic functions
I would like to take this review (after PGCon).
Too late, Bruce applied it already :).
Yes ... Never mind
What's about
- full page writes improvement
but I will have time after
Zdenek Kotala wrote:
Heikki Linnakangas wrote:
Zdenek Kotala wrote:
Heikki Linnakangas wrote:
- heap page diagnostic functions
I would like to take this review (after PGCon).
Too late, Bruce applied it already :).
Yes ... Never mind
You know, the fact that it was applied does not
Alvaro Herrera wrote:
Zdenek Kotala wrote:
Heikki Linnakangas wrote:
Zdenek Kotala wrote:
Heikki Linnakangas wrote:
- heap page diagnostic functions
I would like to take this review (after PGCon).
Too late, Bruce applied it already :).
Yes ... Never mind
You know, the
Alvaro Herrera wrote:
Alvaro Herrera wrote:
Zdenek Kotala wrote:
Heikki Linnakangas wrote:
Zdenek Kotala wrote:
Heikki Linnakangas wrote:
- heap page diagnostic functions
I would like to take this review (after PGCon).
Too late, Bruce applied it already :).
Yes ... Never mind
You know,
On Fri, May 18, 2007 at 12:33:11AM +0800, Cui Shijun wrote:
Thank you for your suggestions, I am thinking about Full page writes
improvement. It seems not so complicated, just fit for a novice like
me.
I'll work on it. :-)
Updated on
On Fri, May 18, 2007 at 03:21:00PM +0200, Zdenek Kotala wrote:
What's about
- full page writes improvement
but I will have time after PGCon.
Added you to the list for that at
http://developer.postgresql.org/index.php/Todo:PatchStatus
--
Jim Nasby
Marc G. Fournier wrote:
--On Wednesday, May 16, 2007 20:09:44 -0400 Bruce Momjian [EMAIL PROTECTED]
wrote:
I think one of the things that is preventing urgency is that everyone
knows we have large patches unapplied, so they know that their lack of
activity is not holding up the
I want to help the reviewing work of ctid chain following enhancement .
I've been studying the souce code which related with that part recently.
:-)
2007/5/17, Dave Page [EMAIL PROTECTED]:
I think we just have to accept that we're gonna have a long feature
freeze period, and ask people to help
Cui Shijun wrote:
I want to help the reviewing work of ctid chain following enhancement .
I've been studying the souce code which related with that part recently.
:-)
Please go ahead :-)
Regards Dave
---(end of broadcast)---
TIP 3: Have you
On 5/17/07, Cui Shijun [EMAIL PROTECTED] wrote:
I want to help the reviewing work of ctid chain following enhancement .
I've been studying the souce code which related with that part recently.
:-)
Tom had objected to this patch on the grounds that it adds complexity
without any significant
Pavan Deolasee wrote:
On 5/17/07, Cui Shijun [EMAIL PROTECTED] wrote:
I want to help the reviewing work of ctid chain following enhancement .
I've been studying the souce code which related with that part recently.
:-)
Tom had objected to this patch on the grounds that it adds
I see...
I checked part of HOT patches(patch1), and found that it involves too
many things I am not currently familar with. Maybe I should change an
item to work. :-(
Since I only studied part of source codes about transaction
processing(lmgr/MVCC/xact but without xlog.c), I want to study
Group
Cui Shijun wrote:
I see...
I checked part of HOT patches(patch1), and found that it involves too
many things I am not currently familar with. Maybe I should change an
item to work. :-(
Yeah, that's one big patch..
Since I only studied part of source codes about transaction
Thank you for your suggestions, I am thinking about Full page writes
improvement. It seems not so complicated, just fit for a novice like
me.
I'll work on it. :-)
2007/5/17, Heikki Linnakangas [EMAIL PROTECTED]:
Cui Shijun wrote:
I see...
I checked part of HOT patches(patch1), and found
Bruce Momjian wrote:
In talking to people who are assigned to review patches or could review
patches, I often get the reply, Oh, yea, I need to do that.
It seems there is a lot of reliance on Tom to get the patches applied,
but I don't think that is fair or reasonable. I think we need more
Bruce, where can I take a look at the patch list in order to find out
if I can be of some help?
Regards,
g.-
On 5/16/07, Bruce Momjian [EMAIL PROTECTED] wrote:
In talking to people who are assigned to review patches or could review
patches, I often get the reply, Oh, yea, I need to do that.
It is all on the developer roadmap page:
http://momjian.us/cgi-bin/pgpatches
---
Guido Barosio wrote:
Bruce, where can I take a look at the patch list in order to find out
if I can be of some help?
Regards,
Bruce Momjian wrote:
It is all on the developer roadmap page:
http://momjian.us/cgi-bin/pgpatches
There is also a slightly more readable one here:
http://developer.postgresql.org/index.php/Todo:PatchStatus
Joshua D. Drake
Bruce Momjian wrote:
In talking to people who are assigned to review patches or could review
patches, I often get the reply, Oh, yea, I need to do that.
Folks, we are six weeks into feature freeze and have made slim progress
on getting patches reviewed and applied. As I stated earlier, we
Joshua D. Drake wrote:
Bruce Momjian wrote:
It is all on the developer roadmap page:
http://momjian.us/cgi-bin/pgpatches
There is also a slightly more readable one here:
http://developer.postgresql.org/index.php/Todo:PatchStatus
note that http://momjian.us/cgi-bin/pgpatches
Andrew Dunstan wrote:
Bruce Momjian wrote:
In talking to people who are assigned to review patches or could review
patches, I often get the reply, Oh, yea, I need to do that.
Folks, we are six weeks into feature freeze and have made slim progress
on getting patches reviewed and
Andrew Dunstan wrote:
Bruce Momjian wrote:
In talking to people who are assigned to review patches or could review
patches, I often get the reply, Oh, yea, I need to do that.
Folks, we are six weeks into feature freeze and have made slim progress
on getting patches reviewed and applied.
What about a mentoring schema in order to push up the gap that
represents catching up with cases like the one Andrew posted?
By the way, being a patch reviewer doesn't represents also to be able
to find out potential problems in the code, which may have nothing to
do with the patch
I think one of the things that is preventing urgency is that everyone
knows we have large patches unapplied, so they know that their lack of
activity is not holding up the release. Any way around that?
---
bruce wrote:
In
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --On Wednesday, May 16, 2007 20:09:44 -0400 Bruce Momjian [EMAIL PROTECTED]
wrote:
I think one of the things that is preventing urgency is that everyone
knows we have large patches unapplied, so they know that their lack of
activity is not
On 5/16/07, Marc G. Fournier [EMAIL PROTECTED] wrote:
Set a fixed date (ie. 3 weeks) and whatever isn't in gets punted to 8.4 ... if
that means those 'large patches' don't get applied, so be it ...
I disagree with that approach. Larger more complex patches required
much more work and effort
Jonah H. Harris wrote:
On 5/16/07, Marc G. Fournier [EMAIL PROTECTED] wrote:
Set a fixed date (ie. 3 weeks) and whatever isn't in gets punted to 8.4 ...
if
that means those 'large patches' don't get applied, so be it ...
I disagree with that approach. Larger more complex patches
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --On Wednesday, May 16, 2007 21:04:27 -0400 Bruce Momjian [EMAIL PROTECTED]
wrote:
Jonah H. Harris wrote:
On 5/16/07, Marc G. Fournier [EMAIL PROTECTED] wrote:
Set a fixed date (ie. 3 weeks) and whatever isn't in gets punted to 8.4
... if
Marc G. Fournier wrote:
Jonah H. Harris wrote:
On 5/16/07, Marc G. Fournier [EMAIL PROTECTED] wrote:
Set a fixed date (ie. 3 weeks) and whatever isn't in gets punted to 8.4
... if that means those 'large patches' don't get applied, so be it ...
I disagree with that approach. Larger
Marc G. Fournier wrote:
I disagree with that approach. Larger more complex patches required
much more work and effort than small, simple ones. Not only do I
think it's unfair to the authors who spent considerably more time on
their work, but I think it also sets a bad precedent for future
On 5/16/07, Bruce Momjian [EMAIL PROTECTED] wrote:
Yep, that is part of our problem, but even items people have already
said they _can_ review have shown little progress.
For complex patches, it might help to identify and associate a core/senior
community member in the early stages of
33 matches
Mail list logo
