On Sat, 28 Jun 2003, Jan Wieck wrote:
> Bruce Momjian wrote:
> > See my recent commit of src/tools/pgtest. It might be a good start.
>
> I was wondering if some existing framework, like from the Apache Xalan
> package, would be a better point to start from? I hate to say it, Bruce,
> but you try
Bruce Momjian wrote:
See my recent commit of src/tools/pgtest. It might be a good start.
I was wondering if some existing framework, like from the Apache Xalan
package, would be a better point to start from? I hate to say it, Bruce,
but you try to reinvent the wheel by starting with a sled.
Jan
Wow, I am impressed by 'gmake check'. Who did all that work? It is
great.
I modified tools/pgtest to use 'gmake check'. Thanks.
---
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > Amazing you find 688 bytes worth
Peter Eisentraut wrote:
>Thomas Swan writes:
>
>
>
>>I just am really concerned about the uninstall/clean up phase and how
>>that can be done in an orderly fashion. Unless the process can start
>>from a clean state again, then it won't be valid.
>>
>>
>
>The only clean state is if you remov
Bruce Momjian writes:
> Amazing you find 688 bytes worth discussing. I know you said "what
> happens if everyone adds their scripts", but something that would be a
> mess if everyone did it isn't always a proper way to judge if something
> is appropriate.
I said, if everyone adds their test meth
Thomas Swan writes:
> I just am really concerned about the uninstall/clean up phase and how
> that can be done in an orderly fashion. Unless the process can start
> from a clean state again, then it won't be valid.
The only clean state is if you remove the entire source tree and check it
out aga
Tom Lane writes:
> This is something that breaks regularly because few of the key
> developers use it :-(. If there were automatic tests that used that
> build setup, it would be a good thing 'cause it'd keep us honest.
This should be included in 'make distcheck'. I'm quite puzzled right now
wh
On Thu, 26 Jun 2003, Bruce Momjian wrote:
>
> See my recent commit of src/tools/pgtest. It might be a good start.
Yes this is a good start. This is a little concerning though:
pg_ctl stop
rm -rf "$PGDATA"
Perhaps a warning is warranted (ie, $PGDATA shouldn't point to your
production data clus
Rod Taylor <[EMAIL PROTECTED]> writes:
> I've not tried, but if PostgreSQL can do an 'out of tree' compile it
> could make it much easier.
Yes it can, following the usual procedure for autoconfiscated trees:
just invoke configure from an empty directory, eg
mkdir build
cd build
See my recent commit of src/tools/pgtest. It might be a good start.
---
Gavin Sherry wrote:
> On Thu, 26 Jun 2003, Kevin Brown wrote:
>
> > The Hermit Hacker wrote:
> > > On Wed, 25 Jun 2003, Kevin Brown wrote:
> > >
> >
On Thu, 26 Jun 2003, Kevin Brown wrote:
> The Hermit Hacker wrote:
> > On Wed, 25 Jun 2003, Kevin Brown wrote:
> >
> > > So...would it make sense to create a gborg project to which people who
> > > have written their own test suites can contribute whatever code and data
> > > they feel comfortabl
On Thu, 26 Jun 2003, Kevin Brown wrote:
> > It doesn't sound like a bad idea ... but, it pretty much comes down to the
> > original thread: are you willing to step up and maintain such a project?
>
> Yes, I am ("how hard can it be?", he asks himself, knowing all the
> while that it's a really bad
The Hermit Hacker wrote:
> On Wed, 25 Jun 2003, Kevin Brown wrote:
>
> > So...would it make sense to create a gborg project to which people who
> > have written their own test suites can contribute whatever code and data
> > they feel comfortable releasing? As a gborg project, it would be
> > sep
The Hermit Hacker wrote:
On Thu, 26 Jun 2003, Thomas Swan wrote:
Of course, these are just ideas and I'm not sure how practical it is to
do any of them. I just am really concerned about the uninstall/clean up
phase and how that can be done in an orderly fashion. Unless the
process can start
On Thu, 26 Jun 2003, Rod Taylor wrote:
> I think we should replace Bruce's pgtest script with this one -- with an
> argument to accept the email address to report to for FAILING cases.
> Success isn't very interesting if it runs regularly.
that was why I suggested getting it into the tree ... to
On Thu, 26 Jun 2003, Thomas Swan wrote:
> Of course, these are just ideas and I'm not sure how practical it is to
> do any of them. I just am really concerned about the uninstall/clean up
> phase and how that can be done in an orderly fashion. Unless the
> process can start from a clean state ag
-Original Message-
From: Rod Taylor [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 26, 2003 3:33 PM
To: Gonyou, Austin
Cc: Thomas Swan; Nigel J. Andrews; Tom Lane; PostgreSQL Development
Subject: RE: Two weeks to feature freeze
On Thu, 2003-06-26 at 16:09, Gonyou, Austin wrote:
> DOH!.
On Thu, 2003-06-26 at 16:09, Gonyou, Austin wrote:
> DOH!. YesYou're right I totally forgot about that. My apologies. I
> believe though, that there is a HP testing lab that is somewhat like OSDL,
> in that they offer OSS free services and many platforms to run on. (used to
> be compaq's develo
> * clean the source, destination directories
> * pull latest CVS tip down.
Why tip? Lets simply update the current source tree to the most current
of whatever branch they had checked out initially.
Running it on older stable branches is just as useful.
> * record environment / inst
DOH!. YesYou're right I totally forgot about that. My apologies. I
believe though, that there is a HP testing lab that is somewhat like OSDL,
in that they offer OSS free services and many platforms to run on. (used to
be compaq's developer testdrive sort of program) I believe it still exists.
On Thu, 2003-06-26 at 15:00, Austin Gonyou wrote:
> I know I'm new to this list, but is OSDL's testing capabilities out of
> the question?
From what I've seen, OSDL is only concerned with a very very small set
of platforms (Linux in a couple of configurations).
--
Rod Taylor <[EMAIL PROTECTED]>
I know I'm new to this list, but is OSDL's testing capabilities out of
the question?
On Thu, 2003-06-26 at 13:48, Thomas Swan wrote:
> Nigel J. Andrews wrote:
>
> >On Thu, 26 Jun 2003, Thomas Swan wrote:
> >
> >
> >>Is it possible the sourceforge compile farms could be used for some of
> >>th
Nigel J. Andrews wrote:
>On Thu, 26 Jun 2003, Thomas Swan wrote:
>
>
>>Is it possible the sourceforge compile farms could be used for some of
>>the automated testing? I'm not sure how that system works, but it could
>>be worth looking into.
>>
>>
>
>Isn't the sourceforge license very scar
On Thu, 26 Jun 2003, Thomas Swan wrote:
> >
> Is it possible the sourceforge compile farms could be used for some of
> the automated testing? I'm not sure how that system works, but it could
> be worth looking into.
Isn't the sourceforge license very scary and along the lines of "whatever you
Thomas Swan <[EMAIL PROTECTED]> writes:
> Is it possible the sourceforge compile farms could be used for some of
> the automated testing? I'm not sure how that system works, but it could
> be worth looking into.
The last time I used it (which admittedly was a year or two back), they
didn't real
Tom Lane wrote:
Peter Eisentraut <[EMAIL PROTECTED]> writes:
Thomas Swan writes:
Have you considered something similar to the Mozilla tinderbox approach
where you have a daemon checkout the cvs, compile, run regression tests,
and report a status or be able to report a status?
Eve
Doesn't matter, this entire approach has a fundamental flaw. If the
lungs are "empty" ... that means that the guy has an open thorax, the
lungs are collapsed, and you'll probably have problems catching his
attention to make your claim.
Jan
The Hermit Hacker wrote:
On Wed, 25 Jun 2003, Shridhar
On Wed, 25 Jun 2003, Kevin Brown wrote:
> So...would it make sense to create a gborg project to which people who
> have written their own test suites can contribute whatever code and data
> they feel comfortable releasing? As a gborg project, it would be
> separate from the main PG distribution a
On Wed, 25 Jun 2003, Shridhar Daithankar wrote:
> On 25 Jun 2003 at 14:50, Andreas Pflug wrote:
> > Jan Wieck wrote:
> > > Change that into "* Remove bugs from source code" and get a patent on
> > > it. Should be a nobrainer (as in those guy's have no brains)
> > > considering that NetFlix even go
Kevin,
> So...would it make sense to create a gborg project to which people who
> have written their own test suites can contribute whatever code and
> data they feel comfortable releasing? As a gborg project, it would be
> separate from the main PG distribution and would thus have no impact on
>
Tom Lane wrote:
> Josh Berkus <[EMAIL PROTECTED]> writes:
> > 3) Dann is proposing not just a feature but sweeping changes to the way our
> > commmunity works, despite having been a member of this community for about 3
> > weeks total.
>
> In Dann's defense, I didn't think I heard him proposing
Josh Berkus <[EMAIL PROTECTED]> writes:
> 3) Dann is proposing not just a feature but sweeping changes to the way our
> commmunity works, despite having been a member of this community for about 3
> weeks total.
In Dann's defense, I didn't think I heard him proposing that we get rid
of our exist
Jan,
> There have been a good number of examples where the one who raised an
> issue isn't just of the format to implement it. So someone else jumped
> in and did it instead. I don't need to pick any particular samples, you
> know that it happened a few times.
Sure. But in those cases, the fix/f
> Change that into "* Remove bugs from source code" and get a patent on
> it. Should be a nobrainer (as in those guy's have no brains) considering
> that NetFlix even got a patent on DVD subscription rentals:
And for all the nice royalty money*, think about what can be done to
PostgreSQL. Maybe e
On 25 Jun 2003 at 14:50, Andreas Pflug wrote:
> Jan Wieck wrote:
> > Change that into "* Remove bugs from source code" and get a patent on
> > it. Should be a nobrainer (as in those guy's have no brains)
> > considering that NetFlix even got a patent on DVD subscription rentals:
> >
> > http://sl
Jan Wieck wrote:
Change that into "* Remove bugs from source code" and get a patent on
it. Should be a nobrainer (as in those guy's have no brains)
considering that NetFlix even got a patent on DVD subscription rentals:
http://slashdot.org/article.pl?sid=03/06/24/1458223&mode=flat&tid=155&tid=9
Kaare Rasmussen wrote:
> That seems too vague for TODO. We might as well add "Make PostgreSQL
> faster". :-)
'K, can you add that one too? :)
How about "* Remove all bugs from the source". Can you put that in TODO ?
:-)
Change that into "* Remove bugs from source code" and get a patent on
it.
> > That seems too vague for TODO. We might as well add "Make PostgreSQL
> > faster". :-)
> 'K, can you add that one too? :)
How about "* Remove all bugs from the source". Can you put that in TODO ?
:-)
--
Kaare Rasmussen--Linux, spil,--Tlf:3816 2582
Kaki Data
an; Tom Lane; Jason Earl; PostgreSQL-development
> > Subject: RE: [HACKERS] Two weeks to feature freeze
> >
> >
> > On Tue, 24 Jun 2003, Dann Corbit wrote:
> >
> > > I did something about it. I raised the issue.
> > > Is it really so that whoever it is
On Tue, 24 Jun 2003, Jan Wieck wrote:
> The Hermit Hacker wrote:
> > On Tue, 24 Jun 2003, Bruce Momjian wrote:
> >
> >> The Hermit Hacker wrote:
> >> > On Tue, 24 Jun 2003, Dann Corbit wrote:
> >> >
> >> > > I did something about it. I raised the issue.
> >> > > Is it really so that whoever it is
The Hermit Hacker wrote:
On Tue, 24 Jun 2003, Bruce Momjian wrote:
The Hermit Hacker wrote:
> On Tue, 24 Jun 2003, Dann Corbit wrote:
>
> > I did something about it. I raised the issue.
> > Is it really so that whoever it is that raises a question is also the
> > one who must fix the issue raised
The Hermit Hacker wrote:
On Tue, 24 Jun 2003, Dann Corbit wrote:
I did something about it. I raised the issue.
Is it really so that whoever it is that raises a question is also the
one who must fix the issue raised?
A strange model indeed.
Its worked for us ...
Sorry Marc, but that ain't entirely
On Tue, 24 Jun 2003, Dann Corbit wrote:
> > > Don't care and won't do are not the same thing.
> >
> > Well, actually, they are ... if someone doesn't care, they
> > aren't going to do, are they?
>
> You have had the time to do everything you ever cared about?
No no, that isn't what he is arguing
On Tue, 24 Jun 2003, Bruce Momjian wrote:
> The Hermit Hacker wrote:
> > On Tue, 24 Jun 2003, Dann Corbit wrote:
> >
> > > I did something about it. I raised the issue.
> > > Is it really so that whoever it is that raises a question is also the
> > > one who must fix the issue raised?
> > > A str
t; -Original Message-
> > From: The Hermit Hacker [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, June 24, 2003 6:10 PM
> > To: Dann Corbit
> > Cc: The Hermit Hacker; Jan Wieck; scott.marlowe; Bruce
> > Momjian; Tom Lane; Jason Earl; PostgreSQL-development
&
> -Original Message-
> From: The Hermit Hacker [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 24, 2003 6:10 PM
> To: Dann Corbit
> Cc: The Hermit Hacker; Jan Wieck; scott.marlowe; Bruce
> Momjian; Tom Lane; Jason Earl; PostgreSQL-development
> Subject: RE: [HACKERS]
The Hermit Hacker wrote:
> On Tue, 24 Jun 2003, Dann Corbit wrote:
>
> > I did something about it. I raised the issue.
> > Is it really so that whoever it is that raises a question is also the
> > one who must fix the issue raised?
> > A strange model indeed.
>
> Its worked for us ...
>
> Wait,
On Tue, 24 Jun 2003, Dann Corbit wrote:
> I did something about it. I raised the issue.
> Is it really so that whoever it is that raises a question is also the
> one who must fix the issue raised?
> A strange model indeed.
Its worked for us ...
Wait, I know what should make you happy ... it won
> -Original Message-
> From: The Hermit Hacker [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 24, 2003 5:26 PM
> To: Dann Corbit
> Cc: Jan Wieck; scott.marlowe; Bruce Momjian; Tom Lane; Jason
> Earl; PostgreSQL-development
> Subject: Re: [HACKERS] Two weeks to feat
On Tue, 24 Jun 2003, Robert Treat wrote:
> On Mon, 2003-06-23 at 21:36, The Hermit Hacker wrote:
> > On Mon, 23 Jun 2003, Robert Treat wrote:
> >
> > > > The target-date-based approach we've taken in the last couple of
> > > > releases seems much more productive.
> > > >
> > >
> > > productive on
On Mon, 23 Jun 2003, Dann Corbit wrote:
> > Would it be nice if we had more tests? Yes. In fact, one of
> > the items on my
> > personal todo list is to devise a more versatile performance
> > test than
> > pgbench for testing postgresql parameters, builds, and
> > installations. But
> > it's n
pment
> > Subject: Re: [HACKERS] Two weeks to feature freeze
> [snip]
> > I personally think you don't actually ever did any software testing
> > yourself. You are not really talking from experience, are you? So
> > please, show me what you have now, or get one more plu
'K, and do you have any ETA on when you'll have this translated into some
useful tests that we can incorporate?
On Mon, 23 Jun 2003, Dann Corbit wrote:
> Here is a list of a small sample of the citations available from the ACM
> on software testing:
>
> http://portal.acm.org/citation.cfm?id=5813
Robert Treat wrote:
> the whole discussion is based on how do we get big projects done when no
> one is motivated to work on 'foo' until there faced with a deadline;
> this idea puts the pressure on 'foo' developers from the get go. i'm not
> saying this a guaranteed way to solve that problem but
On Mon, 2003-06-23 at 21:36, The Hermit Hacker wrote:
> On Mon, 23 Jun 2003, Robert Treat wrote:
>
> > > The target-date-based approach we've taken in the last couple of
> > > releases seems much more productive.
> > >
> >
> > productive on a small scale; for sure. productive for large scale
> > f
Dann Corbit wrote:
-Original Message-
From: Jan Wieck [mailto:[EMAIL PROTECTED]
Sent: Monday, June 23, 2003 10:30 PM
To: Dann Corbit
Cc: scott.marlowe; Bruce Momjian; Tom Lane; Jason Earl;
PostgreSQL-development
Subject: Re: [HACKERS] Two weeks to feature freeze
[snip]
I personally think
> -Original Message-
> From: Josh Berkus [mailto:[EMAIL PROTECTED]
> Sent: Monday, June 23, 2003 10:50 PM
> To: Dann Corbit; Jan Wieck
> Cc: scott.marlowe; Bruce Momjian; Tom Lane; Jason Earl;
> PostgreSQL-development
> Subject: Re: [HACKERS] Two weeks to featur
Dann,
> Astute members of the list have noticed that I have not volunteered to
> perform the work. I may or may not produce some efforts towards testing
> PostgreSQL. Whether I decide to help or not is irrelevant towards the
> concept of what needs to be done.
It is not irrelevant. This is an
> -Original Message-
> From: Jan Wieck [mailto:[EMAIL PROTECTED]
> Sent: Monday, June 23, 2003 10:30 PM
> To: Dann Corbit
> Cc: scott.marlowe; Bruce Momjian; Tom Lane; Jason Earl;
> PostgreSQL-development
> Subject: Re: [HACKERS] Two weeks to feature freeze
[snip]
Dann Corbit wrote:
-Original Message-
From: Jan Wieck [mailto:[EMAIL PROTECTED]
Sent: Monday, June 23, 2003 10:10 PM
To: scott.marlowe
Cc: Dann Corbit; Bruce Momjian; Tom Lane; Jason Earl;
PostgreSQL-development
Subject: Re: [HACKERS] Two weeks to feature freeze
scott.marlowe wrote
Here is a list of a small sample of the citations available from the ACM
on software testing:
http://portal.acm.org/citation.cfm?id=581358&coll=portal&dl=ACM&CFID=657
0092&CFTOKEN=81653602
http://portal.acm.org/citation.cfm?id=376180&coll=portal&dl=ACM&CFID=657
0092&CFTOKEN=81653602
http://portal.
> -Original Message-
> From: Jan Wieck [mailto:[EMAIL PROTECTED]
> Sent: Monday, June 23, 2003 10:10 PM
> To: scott.marlowe
> Cc: Dann Corbit; Bruce Momjian; Tom Lane; Jason Earl;
> PostgreSQL-development
> Subject: Re: [HACKERS] Two weeks to feature freeze
>
scott.marlowe wrote:
On Mon, 23 Jun 2003, Dann Corbit wrote:
> [Dann Corbit wrote a lot]
> [...]
It may be reassuring to think your product is very well tested before it
goes out the door, but it's a false security, proven over and over by
commercial products that simply don't work in the field b
Dann Corbit wrote:
-Original Message-
From: Jan Wieck [mailto:[EMAIL PROTECTED]
What do you think is the way to become an insider?
Join the CVS tree and make a large and valuable contribution to the
project.
Go ahead, let's see it.
I have contributed a lot of crap over the years. After s
Thank's Robert,
that was probably what Bruce needs to call me every other hour now ...
Jan
Robert Treat wrote:
On Sat, 2003-06-21 at 22:55, Bruce Momjian wrote:
Andrew Dunstan wrote:
>
> Maybe a better strategy would be to get a release out soon but not wait 6
> months for another release which
On Mon, 23 Jun 2003, Dann Corbit wrote:
> The resistance to testing is typical of programmers. The PostgreSQL
> group is a group of programmers. I don't think I can change anyone's
> mind, since the most significant people on the list don't think it is
> worth the bother.
>
> Therefore, I am goi
On Mon, 23 Jun 2003, Robert Treat wrote:
> > The target-date-based approach we've taken in the last couple of
> > releases seems much more productive.
> >
>
> productive on a small scale; for sure. productive for large scale
> features... well, that's why it's being discussed.
'K, but if we exte
On Monday 23 June 2003 15:42, Dann Corbit wrote:
> Let me rephrase it:
> "Only a cohesive, organized testing effort can result in a product that
> is proven reliable."
One can never 100% prove reliability without time in the field with real-world
data, testing or no testing. I would dare say th
> -Original Message-
> From: Nigel J. Andrews [mailto:[EMAIL PROTECTED]
> Sent: Monday, June 23, 2003 1:30 PM
> To: Dann Corbit
> Cc: scott.marlowe; Bruce Momjian; Tom Lane; Jason Earl;
> PostgreSQL-development
> Subject: Re: [HACKERS] Two weeks to feature freeze
[sn
On Mon, 23 Jun 2003, Dann Corbit wrote:
> > -Original Message-
> > From: scott.marlowe [mailto:[EMAIL PROTECTED]
> > Sent: Monday, June 23, 2003 12:25 PM
> > To: Dann Corbit
> > Cc: Bruce Momjian; Tom Lane; Jason Earl; PostgreSQL-development
> >
On Mon, 23 Jun 2003, Dann Corbit wrote:
> > -Original Message-
> > From: scott.marlowe [mailto:[EMAIL PROTECTED]
> > Sent: Monday, June 23, 2003 12:25 PM
> > To: Dann Corbit
> > Cc: Bruce Momjian; Tom Lane; Jason Earl; PostgreSQL-development
> >
Dann Corbit wrote:
> Let me rephrase it:
> "Only a cohesive, organized testing effort can result in a product that
> is proven reliable."
>
> Without such an effort, it is only an educated guess as to whether the
> product is reliable or not. The data is the most valuable software
> component in
scott.marlowe wrote:
> Peter is coming off awfully paternalistic here. I'd rather have a few
> extra scripts to look through to find what I need when I'm trying to
> figure out something than to have a tool that only the hackers know exists
> and I can only get by asking nicely to see the prett
> -Original Message-
> From: scott.marlowe [mailto:[EMAIL PROTECTED]
> Sent: Monday, June 23, 2003 12:25 PM
> To: Dann Corbit
> Cc: Bruce Momjian; Tom Lane; Jason Earl; PostgreSQL-development
> Subject: Re: [HACKERS] Two weeks to feature freeze
>
>
> On Mo
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > I put stuff in /tools so if something happens to me, you guys can keep
> > going.
>
> Yes, we keep going with make clean; make check, like everyone else. Why
> don't you consider using that?
Actually, I used to manually do all those tests to
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > I put stuff in /tools so if something happens to me, you guys can keep
> > going.
>
> Yes, we keep going with make clean; make check, like everyone else. Why
> don't you consider using that?
The script is automated to run at night, it captur
On Mon, 23 Jun 2003, Bruce Momjian wrote:
> Peter Eisentraut wrote:
> > Bruce Momjian writes:
> >
> > > Well, it is a nice test template for people who aren't shell script
> > > experts, and I have been in the habit of pushing stuff I use into /tools
> > > so it is available for others.
> >
> >
On Mon, 23 Jun 2003, Dann Corbit wrote:
> Vendor A: "We think our tool is pretty solid and our end users hardly
> ever turn up any bugs."
>
> Vendor B:" We think our tool is pretty solid and our 8500 tests
> currently show only 3 defects with the released version, and these are
> low impact issue
Bruce Momjian writes:
> I put stuff in /tools so if something happens to me, you guys can keep
> going.
Yes, we keep going with make clean; make check, like everyone else. Why
don't you consider using that?
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)
Dann Corbit wrote:
> PostgreSQL is a fairly mature product, having been in existence in one
> form or another for many years now.
>
> I expect that most of the bugs that surface will be in areas of new
> functionality.
>
> Great Bridge had the right idea though. Let's suppose that they ran
> 10,
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > Well, it is a nice test template for people who aren't shell script
> > experts, and I have been in the habit of pushing stuff I use into /tools
> > so it is available for others.
>
> I know and I'm not happy about it. The PostgreSQL source t
> -Original Message-
> From: Bruce Momjian [mailto:[EMAIL PROTECTED]
> Sent: Saturday, June 21, 2003 8:50 PM
> To: Dann Corbit
> Cc: Tom Lane; Jason Earl; PostgreSQL-development
> Subject: Re: [HACKERS] Two weeks to feature freeze
>
>
> Dann Corbit wrote:
>
"Dann Corbit" <[EMAIL PROTECTED]> writes:
>> What do you think is the way to become an insider?
> Join the CVS tree and make a large and valuable contribution to the
> project.
For instance, developing an industrial-strength test suite? If you've
got an itch there, scratch it.
Bruce Momjian writes:
> Well, it is a nice test template for people who aren't shell script
> experts, and I have been in the habit of pushing stuff I use into /tools
> so it is available for others.
I know and I'm not happy about it. The PostgreSQL source tree isn't a
repository of everyone's f
> -Original Message-
> From: Jan Wieck [mailto:[EMAIL PROTECTED]
> Sent: Sunday, June 22, 2003 5:45 AM
> To: Dann Corbit
> Cc: Tom Lane; Jason Earl; PostgreSQL-development
> Subject: Re: [HACKERS] Two weeks to feature freeze
>
>
> Dann Corbit wrote:
> -Original Message-
> From: The Hermit Hacker [mailto:[EMAIL PROTECTED]
> Sent: Sunday, June 22, 2003 12:30 PM
> To: Jan Wieck
> Cc: The Hermit Hacker; Dann Corbit; Tom Lane; Jason Earl;
> PostgreSQL-development
> Subject: Re: [HACKERS] Two weeks to feature freeze
&
Scott MArlowe wrote:
> On Sat, 21 Jun 2003, Bruce Momjian wrote:
>
>> The big puzzle is how do you get people (including myself) motivated
>> to work on a feature that takes a _huge_ amount of work to see any
>> payoff? I would like to know. Anyone?
>
> Pizza? :-)
Unfortunately it's off my die
On Mon, 23 Jun 2003, Bruce Momjian wrote:
> Peter Eisentraut wrote:
> > The Hermit Hacker writes:
> >
> > > Ya, the script looked like it did a bit more then just a 'make clean; make
> > > check' ... doesn't it?
> >
> > No.
>
> Well, it is a nice test template for people who aren't shell script
Robert Treat <[EMAIL PROTECTED]> writes:
> Here's a sure to be wildly unpopular suggestion:
> Make the deciding factor for the next release support of "foo" (foo can
> be win32, pitr, replication, 2PC, whatever...).
We've done that before (see WAL in 7.1), with unhappy results. The
fundamental p
On Monday 23 June 2003 10:43 am, Tom Lane wrote:
> Robert Treat <[EMAIL PROTECTED]> writes:
> > Here's a sure to be wildly unpopular suggestion:
> >
> > Make the deciding factor for the next release support of "foo" (foo can
> > be win32, pitr, replication, 2PC, whatever...).
>
> We've done that be
On Sat, 2003-06-21 at 22:55, Bruce Momjian wrote:
> Andrew Dunstan wrote:
> >
> > Maybe a better strategy would be to get a release out soon but not wait 6
> > months for another release which would contain the Win32 port and the PITR
> > stuff (assuming those aren't done in time for this release)
Peter Eisentraut wrote:
> The Hermit Hacker writes:
>
> > Ya, the script looked like it did a bit more then just a 'make clean; make
> > check' ... doesn't it?
>
> No.
Well, it is a nice test template for people who aren't shell script
experts, and I have been in the habit of pushing stuff I use
The Hermit Hacker writes:
> Ya, the script looked like it did a bit more then just a 'make clean; make
> check' ... doesn't it?
No.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
On Sat, 21 Jun 2003, Bruce Momjian wrote:
> Andrew Dunstan wrote:
> >
> > Maybe a better strategy would be to get a release out soon but not wait 6
> > months for another release which would contain the Win32 port and the PITR
> > stuff (assuming those aren't done in time for this release).
>
>
On Sat, 21 Jun 2003, Christopher Kings-Lynne wrote:
> Crash-me has nothing to do with testing, it jsut checks to see what
> features a db supports:
An interesting point is that until recently, crashme said that the
postgresql backend crashed on very large queries. The actual problem was
that p
I wrote:
> Tom Lane wrote:
>
>>Basically, the subordinate must be willing to hold its breath *forever*.
>
>
> Yep. And if the cohort crashes while waiting for the coordinator to
> come back on-line, if I understand the world correctly, it must be
> capable of committing the database changes a
Tom Lane wrote:
> The Hermit Hacker <[EMAIL PROTECTED]> writes:
>
>>Hrmmm, I see Tom's point (I think!) ... but what if, for instance, the
>>co-ordinator crashes?
>
> Or you just lose the network connection for awhile. The worst case
> scenario I think is where the co-ordinator got everyone's p
> "Tom" == Tom Lane <[EMAIL PROTECTED]> writes:
Tom> Sailesh Krishnamurthy <[EMAIL PROTECTED]> writes:
>> I'm not sure if I understand Tom's beef - I think he is
>> concerned about what happens if a subordinate does not respond
>> to a prepare message. I would assume that the c
The Hermit Hacker <[EMAIL PROTECTED]> writes:
> Hrmmm, I see Tom's point (I think!) ... but what if, for instance, the
> co-ordinator crashes?
Or you just lose the network connection for awhile. The worst case
scenario I think is where the co-ordinator got everyone's promise to
commit, and told s
On Mon, 23 Jun 2003, Christopher Kings-Lynne wrote:
> > No. I want to know what the subordinate does when it's promised to
> > commit and the co-ordinator never responds. AFAICS the subordinate
> > is screwed --- it can't commit, and it can't abort, and it can't expect
> > to make progress indef
1 - 100 of 234 matches
Mail list logo
