Prev: _bt_parent_deletion_safe() isn't safe
Next: Command to prune archive at restartpoints
From: Robert Haas on 8 Jun 2010 21:38
On Tue, Jun 8, 2010 at 6:20 PM, Josh Berkus <josh(a)agliodbs.com> wrote:
>> �If I simply start overhauling the list without explaining what I
>> perceive to be the systematic problems with it, then I will get yelled
>> at for failing to follow community process.
>
> Nonsense. �The one good thing about admin stuff in this community is
> since nobody wants to do it, you seldom get critiqued for how you did
> it. �;-)

OK, list cleaned up. What would be really helpful now is if someone
could try to figure out new items that have come up recently that may
need to be added to the list.

> Brownie points granted. �Although I'd think actual brownies or cookies
> would be better. ;-)

You can email me off-list for my address. :-)

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Simon Riggs on 9 Jun 2010 02:27
On Tue, 2010-06-08 at 15:46 -0400, Tom Lane wrote:
> Josh Berkus <josh(a)agliodbs.com> writes:
> > Let's get 9.0 out the door, hey?
>
> What we actually need is some testing effort. The lack of bug reports
> against Hot Standby, in particular, is proof positive that no meaningful
> testing is happening.

Absence of evidence is not evidence of absence. Please don't confuse
things by claiming "proof positive" does, or even can, exist here.

A lack of bugs usually indicates there are no bugs in the areas being
tested. Which can also mean the areas being tested don't cover the full
code or that tests of anything are not being performed.

I raised the topic of how to increase the amount of testing earlier; my
proposed solution was more betas before we go live. We just guaranteed
even less testing for HS by not fixing things for Beta2.

Would you like me to patch, or are you still intending to look at
max_standby_delay yourself?

> (If you think it means HS is bug-free, I have a
> nice bridge I'd like to interest you in.)

How should we proceed?

--
Simon Riggs www.2ndQuadrant.com


--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Greg Stark on 9 Jun 2010 06:34
On Wed, Jun 9, 2010 at 7:27 AM, Simon Riggs <simon(a)2ndquadrant.com> wrote:
....
> Absence of evidence is not evidence of absence.
....
> A lack of bugs usually indicates there are no bugs in the areas being
> tested.

Would the real Simon Riggs please speak up? Isn't that precisely what
"absence of evidence is not evidence of absence" is meant to refute?

--
greg

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Alvaro Herrera on 9 Jun 2010 15:01
Excerpts from Robert Haas's message of mar jun 08 17:01:28 -0400 2010:

> I think only one of them has
> an actual patch associated with it, viz:
>
> ALTER TABLE .. DISABLE/ENABLE TRIGGER are out of date
>
> I took a look at that patch, and I expect it's probably correct, but I
> haven't actually looked at the code to verify that it's correct, so I
> didn't apply it.

I checked the behavior and the patch is correct, so I applied it.

Thanks for clearing the list. There are only 5 remaining items, which
is kinda exciting, though Tom's assertion that HS is still bug-ridden is
a bit off-putting.

--
Álvaro Herrera <alvherre(a)commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Simon Riggs on 9 Jun 2010 16:57
On Wed, 2010-06-09 at 11:34 +0100, Greg Stark wrote:
> On Wed, Jun 9, 2010 at 7:27 AM, Simon Riggs <simon(a)2ndquadrant.com> wrote:
> ...
> > Absence of evidence is not evidence of absence.
> ...
> > A lack of bugs usually indicates there are no bugs in the areas being
> > tested.
>
> Would the real Simon Riggs please speak up?

LOL, its me, flaws included.

> Isn't that precisely what
> "absence of evidence is not evidence of absence" is meant to refute?

You snipped out the part where I give other possible explanations also,
so the two statements above do not counterpoise each other of themselves
in my original text. I stand by my whole statement, as intended.

Now, I think I misread Tom's comments. I agree with Tom that the new bug
discovery rate has fallen to zero and that probably indicates that no
new/ground-breaking tests are taking place.

--
Simon Riggs www.2ndQuadrant.com


--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: _bt_parent_deletion_safe() isn't safe
Next: Command to prune archive at restartpoints