Jeremy Drake wrote:
rsync -avzCH --delete rsync.postgresql.org::pgsql-cvs cvsroot/
The buildfarm howto has somewhat more complete instructions (including
how to adjust the various cvs config files if you need to). I set it up
the other day - took me about 10 minutes.
http://pgfoundry.
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
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
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/24/07, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
Pavan Deolasee: HOT ( never met him )
I am working on it with the target of 8.3. I am posting WIP patches
since couple of weeks. One of the objectives of publishing WIP
patches, even though they are not well tested (for correctness as
we
Please see the attached WIP HOT patch - version 3.2. It now
implements the logic for reusing heap-only dead tuples. When a
HOT-update chain is pruned, the heap-only tuples are marked
LP_DELETE. The lp_offset and lp_len fields in the line pointer are
maintained.
When a backend runs out of free
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
> 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 Saturday 24 February 2007 00:55, Magnus Hagander wrote:
> AFAIK, git still does not support windows properly[1], which I would say
> is a killer... Unless you can of course to everything you need through
> one of those frontend protocols, but if you can do everything that way
> then why would yo
On Saturday 24 February 2007 00:24, Warren Turkal wrote:
> The interesting thing about Git is that is has two way sync support for a
> SVN repository also. You could run a Git repository pushing changes in real
> time to a SVN repository and present a CVS frontend also. I would like to
> try conver
Warren Turkal wrote:
> On Saturday 24 February 2007 00:24, Warren Turkal wrote:
>> The interesting thing about Git is that is has two way sync support for a
>> SVN repository also. You could run a Git repository pushing changes in real
>> time to a SVN repository and present a CVS frontend also. I
Warren Turkal wrote:
On Saturday 24 February 2007 00:55, Magnus Hagander wrote:
AFAIK, git still does not support windows properly[1], which I would say
is a killer... Unless you can of course to everything you need through
one of those frontend protocols, but if you can do everything that wa
Joshua D. Drake wrote:
> Warren Turkal wrote:
> > As a followup, the cvs2svn conversion says the following.
> >
> > Error summary:
> > ERROR: Multiple definitions of the symbol 'creation' in
> > '../pgsql-cvs/cvsroot/pgsql/src/interfaces/perl5/Attic/test.pl.newstyle,v'
> > ERROR: Multiple defini
On Saturday 24 February 2007 15:18, Alvaro Herrera wrote:
> Keep in mind that the repository as converted by Josh, above, is
> strangely corrupted in weird and unpredictable ways.
Would you care to elaborate on that statement? I'd like to check my converted
repositories for what you're referring
Alvaro Herrera wrote:
> Joshua D. Drake wrote:
>> Warren Turkal wrote:
>
>>> As a followup, the cvs2svn conversion says the following.
>>>
>>> Error summary:
>>> ERROR: Multiple definitions of the symbol 'creation' in
>>> '../pgsql-cvs/cvsroot/pgsql/src/interfaces/perl5/Attic/test.pl.newstyle,v'
Warren Turkal wrote:
> On Saturday 24 February 2007 15:18, Alvaro Herrera wrote:
> > Keep in mind that the repository as converted by Josh, above, is
> > strangely corrupted in weird and unpredictable ways.
>
> Would you care to elaborate on that statement? I'd like to check my
> converted reposit
On 2/24/07, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
>>> ERROR: Multiple definitions of the symbol 'creation' in
'../pgsql-cvs/cvsroot/pgsql/src/interfaces/perl5/Attic/test.pl.newstyle,v'
>>> ERROR: Multiple definitions of the symbol 'creation' in
'../pgsql-cvs/cvsroot/pgsql/src/interfaces/per
On 2/24/07, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
I don't know :-( I've tried to use the Trac site looking for particular
changesets and found that for some of them, the list of files are out of
sync with reality, and sometimes the diff don't have anything to do with
what the commit message
Christopher Browne wrote:
> A long time ago, in a galaxy far, far away, [EMAIL PROTECTED] (Hideyuki
> Kawashima) wrote:
>> I appreciate your great suggestion!
>> It is great honor for me if Sigres will be merged to PostgreSQL.
>> Since the changes of Sigres from PostgreSQL-8.2.1 are not many,
>> a
On Saturday 24 February 2007 16:47, Chad Wagner wrote:
> head pgsql/src/interfaces/perl5/Attic/test.pl.oldstyle,v
> head 1.3;
> access;
> symbols
> Release-1-6-0:1.1.1.1
> creation:1.1.1.1
> creation:1.1.1; <<< What the heck happened here?
> locks; strict;
> comment @#
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
On Friday 23 February 2007 11:11, Joshua D. Drake wrote:
> If you are looking for a CVS replacement, that replacement is SVN. I
> don't think anyone can reasonably argue against that statement.
It seems to me that the best reason for keeping CVS is that the build farm
uses it. There are solutions
Warren Turkal <[EMAIL PROTECTED]> writes:
> What would you all think about moving to SVN if the anon CVS checkout can be
> made to work? I'll even volunteer to set it up.
What's with the high pressure sales tactics? It's already been
explained to you that the key PG developers feel no particular
Hallo to all,
Just wondering after reading so many mails from Hackers List.(its 2.15 AM now!!)
Is there anybody working on something to create a DB from
a) The TODO list http://www.postgresql.org/docs/faqs.TODO.html
b) The sourcecode of PostgreSQL
c) The relevant Mailings from the developers lists
Tom Lane <[EMAIL PROTECTED]> writes:
> Warren Turkal <[EMAIL PROTECTED]> writes:
>> What would you all think about moving to SVN if the anon CVS checkout can be
>> made to work? I'll even volunteer to set it up.
>
> What's with the high pressure sales tactics? It's already been
> explained to yo
On Saturday 24 February 2007 19:18, Tom Lane wrote:
> What's with the high pressure sales tactics? It's already been
> explained to you that the key PG developers feel no particular reason
> to change at this time.
I am not trying to be high pressure. I just wanted to give something back to
the
I would like to fund some of the development of the PERIOD datatype that I
mentioned earlier. Are there any developers out there that are interested in
working on this project? I run a business that has a bit of funding for open
source work, and I think this would be a good use of the funding.
On Saturday 24 February 2007 19:51, Douglas McNaught wrote:
> Not to mention that the beginning of feature freeze sounds like a
> particularly bad time to do this. :)
I never encouraged doing it right now, but I'd like to help when and if it
does happen. I think at the begginning of a new dev cy
Douglas McNaught wrote:
Tom Lane <[EMAIL PROTECTED]> writes:
Warren Turkal <[EMAIL PROTECTED]> writes:
What would you all think about moving to SVN if the anon CVS checkout can be
made to work? I'll even volunteer to set it up.
What's with the high pressure sales tactics? It's
Warren Turkal wrote:
On Saturday 24 February 2007 19:51, Douglas McNaught wrote:
Not to mention that the beginning of feature freeze sounds like a
particularly bad time to do this. :)
I never encouraged doing it right now, but I'd like to help when and if it
does happen. I think at t
On Saturday 24 February 2007 20:27, Andrew Dunstan wrote:
> If we were to move now then subversion would probably be the best
> choice, on maturity grounds if nothing else. That might well not be true
> in a year or two. I don't want to move more than once, so waiting and
> seeing makes a lot of se
[EMAIL PROTECTED] wrote:
> Hallo to all,
>
> Just wondering after reading so many mails from Hackers List.(its 2.15 AM
> now!!)
> Is there anybody working on something to create a DB from
What?
Joshua D. Drake
> a) The TODO list http://www.postgresql.org/docs/faqs.TODO.html
> b) The sourcecode
> Warren,
>
> what part of "We'd like to watch the SCM space for a while before making
> any decisions" don't you understand?
Andrew hold on,
He didn't say *which* dev cycle. He is just enthusiastic and the reality
is this project is about 2 years overdue to run screaming from the
burning build
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> Lastly, who really cares? Does it really matter? No. I would much rather
> Warren (if he has the skills) put some effort into Patch Review.
That's pretty much the bottom line. CVS is not so broken that it's a
problem for us today. I have no doubt t
Tom Lane wrote:
> I also tend to think that a conversion will be easier in a year or two
> than it is today --- the problems noted upthread are certainly a
> heads-up that cvs2svn is not yet as robust as one could wish.
Yes, which is why Markus is working on improved algorithms for Monotone.
--
The attached sql file creates some table infrastructure and then tries to
explain a query. I get the following error on CVS HEAD:
psql:bogus_varattno_error.sql:23: ERROR: bogus varattno for OUTER var: 5
In my real data, when I attempt to run the query I get the error:
ERROR: invalid attribute
36 matches
Mail list logo
