Re: [HACKERS] Re: pg_dump possible fix, need testers.

From: Alfred Perlstein <bright(at)wintelcom(dot)net>
To: prlw1(at)cam(dot)ac(dot)uk
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Re: pg_dump possible fix, need testers.
Date: 2000-01-25 01:30:49
Message-ID: 20000124173048.P26520@fw.wintelcom.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk> [000124 16:02] wrote:
> On Mon, Jan 24, 2000 at 03:49:26PM -0800, Alfred Perlstein wrote:
> > I just ran the regression tests as best as I know how:
> >
> > ~/pgcvs/pgsql/src/test/regress % gmake runcheck
> > ~/pgcvs/pgsql/src/test/regress % grep FAIL run_check.out
> > test int2 ... FAILED
> > test int4 ... FAILED
> > test float8 ... FAILED
> > sequential test geometry ... FAILED
> > ~/pgcvs/pgsql/src/test/regress %
> >
> > no int2/int4? yipes!
>
> Not to worry, those will be differences in error message wording, but
>
> > I ran it 10 more times and one time I got:
> > test constraints ... FAILED
>
> What did this error come from? (cf regression.diffs)
>
> > but i got no weird parse errors or anything from the backend.
> >
> > Have you been able to find any weirdness with the fix I posted,
> > or is this more likely an issue with Patrick Welche's setup?
>
> I'm not sure: on the one hand, that evil join of mine returns the entire
> contents of a table, and the connection gets confused. Smaller joins work.
> Maybe it doesn't happen to you because you don't put in such a useless
> select (What do you want 750440 rows for?) On the other hand vacuum analyze
> table_name doesn't work for me but obviously does for everyone else, so at
> least something is wrong with my setup.

whoa whoa whoa... I just updated my snapshot to today's code and lot
more seems broken:

10 runs of the regression test:

test aggregates ... FAILED
test alter_table ... FAILED
test btree_index ... FAILED
test create_misc ... FAILED
test create_operator ... FAILED
test float8 ... FAILED
test hash_index ... FAILED
test int2 ... FAILED
test int4 ... FAILED
test limit ... FAILED
test portals ... FAILED
test portals_p2 ... FAILED
test random ... FAILED
test rules ... FAILED
test select_distinct ... FAILED
test select_distinct_on ... FAILED
test select_views ... FAILED
test transactions ... FAILED
test triggers ... FAILED
sequential test create_type ... FAILED
sequential test create_view ... FAILED
sequential test geometry ... FAILED
sequential test select ... FAILED

I'm going to see what happens if i revert my changes
to libpq completely, but before updating from and old
repo of 2-3 daysall i get are the int/float single constraints
error.

runtests and regression diffs are at:
http://www.freebsd.org/~alfred/postgresql/

-Alfred

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message The Hermit Hacker 2000-01-25 01:34:48 Re: [HACKERS] Well, then you keep your darn columns
Previous Message Tom Lane 2000-01-25 00:25:43 Re: [HACKERS] Happy column dropping