Обсуждение: Massive regression failures

Поиск
Список
Период
Сортировка

Massive regression failures

От
Bruce Momjian
Дата:
I am seeing massive regression failures on a freshly compiled, initdb'ed
version of CVS:
16 of 81 tests failed, 1 of these failures ignored. 

The first failure I see is:  COPY COPY_TBL FROM
'/usr/var/local/src/gen/pgsql/CURRENT/pgsql/src/test/regress/data/constrf.data';-ERROR:  copy: line 2, CopyFrom:
rejecteddue to CHECK constraint copy_con  SELECT * FROM COPY_TBL;   x |       y       | z ! ---+---------------+---!  4
|!check failed | 5!  6 | OK            | 4! (2 rows)
 

Are others seeing this?  Cause?

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


Re: Massive regression failures

От
"Christopher Kings-Lynne"
Дата:
I tried testing it on FreeBSD/Alpha and I only got this far:

./configure --prefix=/home/chriskl/local --enable-integer-datetimes --enable
-debug --enable-depend --enable-cassert --with-pam --with-openssl --with-CXX

gmake check

gmake[3]: Entering directory `/home/chriskl/pgsql-head/src/backend/libpq'
gcc -pipe -O -g -Wall -Wmissing-prototypes -Wmissing-declarations -I../../..
/src/include   -c -o be-secure.o be-secure.c -MMD
be-secure.c: In function `load_dh_file':
be-secure.c:399: `DEBUG' undeclared (first use in this function)
be-secure.c:399: (Each undeclared identifier is reported only once
be-secure.c:399: for each function it appears in.)
be-secure.c: In function `load_dh_buffer':
be-secure.c:447: `DEBUG' undeclared (first use in this function)
be-secure.c: In function `tmp_dh_cb':
be-secure.c:519: `DEBUG' undeclared (first use in this function)
be-secure.c: In function `info_cb':
be-secure.c:550: `DebugLvl' undeclared (first use in this function)
be-secure.c:556: `DEBUG' undeclared (first use in this function)
be-secure.c: In function `initialize_SSL':
be-secure.c:615: warning: implicit declaration of function `lstat'
be-secure.c:615: `buf' undeclared (first use in this function)
be-secure.c:621: warning: implicit declaration of function `S_ISREG'
be-secure.c: In function `open_server_SSL':
be-secure.c:704: `DEBUG' undeclared (first use in this function)
gmake[3]: *** [be-secure.o] Error 1
gmake[3]: Leaving directory `/home/chriskl/pgsql-head/src/backend/libpq'
gmake[2]: *** [libpq-recursive] Error 2
gmake[2]: Leaving directory `/home/chriskl/pgsql-head/src/backend'
gmake[1]: *** [all] Error 2
gmake[1]: Leaving directory `/home/chriskl/pgsql-head/src'
gmake: *** [all] Error 2

I will now recompile without debug symols or openssl perhaps...?

Chris

> -----Original Message-----
> From: pgsql-hackers-owner@postgresql.org
> [mailto:pgsql-hackers-owner@postgresql.org]On Behalf Of Bruce Momjian
> Sent: Monday, 17 June 2002 3:04 PM
> To: PostgreSQL-development
> Subject: [HACKERS] Massive regression failures
>
>
> I am seeing massive regression failures on a freshly compiled, initdb'ed
> version of CVS:
>
>  16 of 81 tests failed, 1 of these failures ignored.
>
> The first failure I see is:
>
>       COPY COPY_TBL FROM
> '/usr/var/local/src/gen/pgsql/CURRENT/pgsql/src/test/regress/data/
> constrf.data';
>     - ERROR:  copy: line 2, CopyFrom: rejected due to CHECK
> constraint copy_con
>       SELECT * FROM COPY_TBL;
>        x |       y       | z
>     ! ---+---------------+---
>     !  4 | !check failed | 5
>     !  6 | OK            | 4
>     ! (2 rows)
>
> Are others seeing this?  Cause?
>
> --
>   Bruce Momjian                        |  http://candle.pha.pa.us
>   pgman@candle.pha.pa.us               |  (610) 853-3000
>   +  If your life is a hard drive,     |  830 Blythe Avenue
>   +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>



Re: Massive regression failures

От
Bruce Momjian
Дата:
OK, fix committed.  He was using 7.2 elog symbols.  I changed DEBUG to
DEBUG1.  Should compile now.  It was already compiling here.  Not sure
why.  :-)

---------------------------------------------------------------------------

Christopher Kings-Lynne wrote:
> I tried testing it on FreeBSD/Alpha and I only got this far:
> 
> ./configure --prefix=/home/chriskl/local --enable-integer-datetimes --enable
> -debug --enable-depend --enable-cassert --with-pam --with-openssl --with-CXX
> 
> gmake check
> 
> gmake[3]: Entering directory `/home/chriskl/pgsql-head/src/backend/libpq'
> gcc -pipe -O -g -Wall -Wmissing-prototypes -Wmissing-declarations -I../../..
> /src/include   -c -o be-secure.o be-secure.c -MMD
> be-secure.c: In function `load_dh_file':
> be-secure.c:399: `DEBUG' undeclared (first use in this function)
> be-secure.c:399: (Each undeclared identifier is reported only once
> be-secure.c:399: for each function it appears in.)
> be-secure.c: In function `load_dh_buffer':
> be-secure.c:447: `DEBUG' undeclared (first use in this function)
> be-secure.c: In function `tmp_dh_cb':
> be-secure.c:519: `DEBUG' undeclared (first use in this function)
> be-secure.c: In function `info_cb':
> be-secure.c:550: `DebugLvl' undeclared (first use in this function)
> be-secure.c:556: `DEBUG' undeclared (first use in this function)
> be-secure.c: In function `initialize_SSL':
> be-secure.c:615: warning: implicit declaration of function `lstat'
> be-secure.c:615: `buf' undeclared (first use in this function)
> be-secure.c:621: warning: implicit declaration of function `S_ISREG'
> be-secure.c: In function `open_server_SSL':
> be-secure.c:704: `DEBUG' undeclared (first use in this function)
> gmake[3]: *** [be-secure.o] Error 1
> gmake[3]: Leaving directory `/home/chriskl/pgsql-head/src/backend/libpq'
> gmake[2]: *** [libpq-recursive] Error 2
> gmake[2]: Leaving directory `/home/chriskl/pgsql-head/src/backend'
> gmake[1]: *** [all] Error 2
> gmake[1]: Leaving directory `/home/chriskl/pgsql-head/src'
> gmake: *** [all] Error 2
> 
> I will now recompile without debug symols or openssl perhaps...?
> 
> Chris
> 
> > -----Original Message-----
> > From: pgsql-hackers-owner@postgresql.org
> > [mailto:pgsql-hackers-owner@postgresql.org]On Behalf Of Bruce Momjian
> > Sent: Monday, 17 June 2002 3:04 PM
> > To: PostgreSQL-development
> > Subject: [HACKERS] Massive regression failures
> >
> >
> > I am seeing massive regression failures on a freshly compiled, initdb'ed
> > version of CVS:
> >
> >  16 of 81 tests failed, 1 of these failures ignored.
> >
> > The first failure I see is:
> >
> >       COPY COPY_TBL FROM
> > '/usr/var/local/src/gen/pgsql/CURRENT/pgsql/src/test/regress/data/
> > constrf.data';
> >     - ERROR:  copy: line 2, CopyFrom: rejected due to CHECK
> > constraint copy_con
> >       SELECT * FROM COPY_TBL;
> >        x |       y       | z
> >     ! ---+---------------+---
> >     !  4 | !check failed | 5
> >     !  6 | OK            | 4
> >     ! (2 rows)
> >
> > Are others seeing this?  Cause?
> >
> > --
> >   Bruce Momjian                        |  http://candle.pha.pa.us
> >   pgman@candle.pha.pa.us               |  (610) 853-3000
> >   +  If your life is a hard drive,     |  830 Blythe Avenue
> >   +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 3: if posting/reading through Usenet, please send an appropriate
> > subscribe-nomail command to majordomo@postgresql.org so that your
> > message can get through to the mailing list cleanly
> >
> 
> 

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


Re: Massive regression failures

От
"Christopher Kings-Lynne"
Дата:
Hmmm...an update for be-secure.c came through, but now I get this:

gcc -pipe -O -g -Wall -Wmissing-prototypes -Wmissing-declarations -I../../..
/src/include   -c -o be-secure.o be-secure.c -MMD
be-secure.c: In function `info_cb':
be-secure.c:550: `DebugLvl' undeclared (first use in this function)
be-secure.c:550: (Each undeclared identifier is reported only once
be-secure.c:550: for each function it appears in.)
be-secure.c: In function `initialize_SSL':
be-secure.c:615: warning: implicit declaration of function `lstat'
be-secure.c:615: `buf' undeclared (first use in this function)
be-secure.c:621: warning: implicit declaration of function `S_ISREG'

Perhaps the reason you're not seeing it is because you're not linking
against OpenSSL??

Chris


> -----Original Message-----
> From: pgsql-hackers-owner@postgresql.org
> [mailto:pgsql-hackers-owner@postgresql.org]On Behalf Of Bruce Momjian
> Sent: Monday, 17 June 2002 3:33 PM
> To: Christopher Kings-Lynne
> Cc: PostgreSQL-development
> Subject: Re: [HACKERS] Massive regression failures
>
>
>
> OK, fix committed.  He was using 7.2 elog symbols.  I changed DEBUG to
> DEBUG1.  Should compile now.  It was already compiling here.  Not sure
> why.  :-)
>
> ------------------------------------------------------------------
> ---------
>
> Christopher Kings-Lynne wrote:
> > I tried testing it on FreeBSD/Alpha and I only got this far:
> >
> > ./configure --prefix=/home/chriskl/local
> --enable-integer-datetimes --enable
> > -debug --enable-depend --enable-cassert --with-pam
> --with-openssl --with-CXX
> >
> > gmake check
> >
> > gmake[3]: Entering directory
> `/home/chriskl/pgsql-head/src/backend/libpq'
> > gcc -pipe -O -g -Wall -Wmissing-prototypes
> -Wmissing-declarations -I../../..
> > /src/include   -c -o be-secure.o be-secure.c -MMD
> > be-secure.c: In function `load_dh_file':
> > be-secure.c:399: `DEBUG' undeclared (first use in this function)
> > be-secure.c:399: (Each undeclared identifier is reported only once
> > be-secure.c:399: for each function it appears in.)
> > be-secure.c: In function `load_dh_buffer':
> > be-secure.c:447: `DEBUG' undeclared (first use in this function)
> > be-secure.c: In function `tmp_dh_cb':
> > be-secure.c:519: `DEBUG' undeclared (first use in this function)
> > be-secure.c: In function `info_cb':
> > be-secure.c:550: `DebugLvl' undeclared (first use in this function)
> > be-secure.c:556: `DEBUG' undeclared (first use in this function)
> > be-secure.c: In function `initialize_SSL':
> > be-secure.c:615: warning: implicit declaration of function `lstat'
> > be-secure.c:615: `buf' undeclared (first use in this function)
> > be-secure.c:621: warning: implicit declaration of function `S_ISREG'
> > be-secure.c: In function `open_server_SSL':
> > be-secure.c:704: `DEBUG' undeclared (first use in this function)
> > gmake[3]: *** [be-secure.o] Error 1
> > gmake[3]: Leaving directory `/home/chriskl/pgsql-head/src/backend/libpq'
> > gmake[2]: *** [libpq-recursive] Error 2
> > gmake[2]: Leaving directory `/home/chriskl/pgsql-head/src/backend'
> > gmake[1]: *** [all] Error 2
> > gmake[1]: Leaving directory `/home/chriskl/pgsql-head/src'
> > gmake: *** [all] Error 2
> >
> > I will now recompile without debug symols or openssl perhaps...?
> >
> > Chris
> >
> > > -----Original Message-----
> > > From: pgsql-hackers-owner@postgresql.org
> > > [mailto:pgsql-hackers-owner@postgresql.org]On Behalf Of Bruce Momjian
> > > Sent: Monday, 17 June 2002 3:04 PM
> > > To: PostgreSQL-development
> > > Subject: [HACKERS] Massive regression failures
> > >
> > >
> > > I am seeing massive regression failures on a freshly
> compiled, initdb'ed
> > > version of CVS:
> > >
> > >  16 of 81 tests failed, 1 of these failures ignored.
> > >
> > > The first failure I see is:
> > >
> > >       COPY COPY_TBL FROM
> > > '/usr/var/local/src/gen/pgsql/CURRENT/pgsql/src/test/regress/data/
> > > constrf.data';
> > >     - ERROR:  copy: line 2, CopyFrom: rejected due to CHECK
> > > constraint copy_con
> > >       SELECT * FROM COPY_TBL;
> > >        x |       y       | z
> > >     ! ---+---------------+---
> > >     !  4 | !check failed | 5
> > >     !  6 | OK            | 4
> > >     ! (2 rows)
> > >
> > > Are others seeing this?  Cause?
> > >
> > > --
> > >   Bruce Momjian                        |  http://candle.pha.pa.us
> > >   pgman@candle.pha.pa.us               |  (610) 853-3000
> > >   +  If your life is a hard drive,     |  830 Blythe Avenue
> > >   +  Christ can be your backup.        |  Drexel Hill,
> Pennsylvania 19026
> > >
> > > ---------------------------(end of
> broadcast)---------------------------
> > > TIP 3: if posting/reading through Usenet, please send an appropriate
> > > subscribe-nomail command to majordomo@postgresql.org so that your
> > > message can get through to the mailing list cleanly
> > >
> >
> >
>
> --
>   Bruce Momjian                        |  http://candle.pha.pa.us
>   pgman@candle.pha.pa.us               |  (610) 853-3000
>   +  If your life is a hard drive,     |  830 Blythe Avenue
>   +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>



Re: Massive regression failures

От
Tom Lane
Дата:
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> I am seeing massive regression failures on a freshly compiled, initdb'ed
> version of CVS:

That's because you broke the regression test data files.

Kindly unbreak them ASAP.  I had wanted to do a cvs update this morning...
        regards, tom lane


Re: Massive regression failures

От
Bruce Momjian
Дата:
Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > I am seeing massive regression failures on a freshly compiled, initdb'ed
> > version of CVS:
> 
> That's because you broke the regression test data files.

Wow, I had a corrupted CVS regression directory.  I was seeing it during
CVS update failure for the /regression directory, but I ignored it. 
Then I thought I saw a commit touching regression, which didn't make
sense, but I closed the window too soon without investigating.

Later, I deleted the directory and recreated it, but seems I had already
accidentally modified those files.  I don't see any other /regression
changes except /data, so I backed out those changes.  We should be OK
now.

> Kindly unbreak them ASAP.  I had wanted to do a cvs update this morning...

Fixed now.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


Re: Massive regression failures

От
Bruce Momjian
Дата:
OK, fixed.  I didn't have SSL enabled in my test compile.  Doing that
now.  I have fixed the elog flags so this should be OK now.  If I see
any other SSL compile issues I will fix them.

---------------------------------------------------------------------------

Christopher Kings-Lynne wrote:
> Hmmm...an update for be-secure.c came through, but now I get this:
> 
> gcc -pipe -O -g -Wall -Wmissing-prototypes -Wmissing-declarations -I../../..
> /src/include   -c -o be-secure.o be-secure.c -MMD
> be-secure.c: In function `info_cb':
> be-secure.c:550: `DebugLvl' undeclared (first use in this function)
> be-secure.c:550: (Each undeclared identifier is reported only once
> be-secure.c:550: for each function it appears in.)
> be-secure.c: In function `initialize_SSL':
> be-secure.c:615: warning: implicit declaration of function `lstat'
> be-secure.c:615: `buf' undeclared (first use in this function)
> be-secure.c:621: warning: implicit declaration of function `S_ISREG'
> 
> Perhaps the reason you're not seeing it is because you're not linking
> against OpenSSL??
> 
> Chris
> 
> 
> > -----Original Message-----
> > From: pgsql-hackers-owner@postgresql.org
> > [mailto:pgsql-hackers-owner@postgresql.org]On Behalf Of Bruce Momjian
> > Sent: Monday, 17 June 2002 3:33 PM
> > To: Christopher Kings-Lynne
> > Cc: PostgreSQL-development
> > Subject: Re: [HACKERS] Massive regression failures
> >
> >
> >
> > OK, fix committed.  He was using 7.2 elog symbols.  I changed DEBUG to
> > DEBUG1.  Should compile now.  It was already compiling here.  Not sure
> > why.  :-)
> >
> > ------------------------------------------------------------------
> > ---------
> >
> > Christopher Kings-Lynne wrote:
> > > I tried testing it on FreeBSD/Alpha and I only got this far:
> > >
> > > ./configure --prefix=/home/chriskl/local
> > --enable-integer-datetimes --enable
> > > -debug --enable-depend --enable-cassert --with-pam
> > --with-openssl --with-CXX
> > >
> > > gmake check
> > >
> > > gmake[3]: Entering directory
> > `/home/chriskl/pgsql-head/src/backend/libpq'
> > > gcc -pipe -O -g -Wall -Wmissing-prototypes
> > -Wmissing-declarations -I../../..
> > > /src/include   -c -o be-secure.o be-secure.c -MMD
> > > be-secure.c: In function `load_dh_file':
> > > be-secure.c:399: `DEBUG' undeclared (first use in this function)
> > > be-secure.c:399: (Each undeclared identifier is reported only once
> > > be-secure.c:399: for each function it appears in.)
> > > be-secure.c: In function `load_dh_buffer':
> > > be-secure.c:447: `DEBUG' undeclared (first use in this function)
> > > be-secure.c: In function `tmp_dh_cb':
> > > be-secure.c:519: `DEBUG' undeclared (first use in this function)
> > > be-secure.c: In function `info_cb':
> > > be-secure.c:550: `DebugLvl' undeclared (first use in this function)
> > > be-secure.c:556: `DEBUG' undeclared (first use in this function)
> > > be-secure.c: In function `initialize_SSL':
> > > be-secure.c:615: warning: implicit declaration of function `lstat'
> > > be-secure.c:615: `buf' undeclared (first use in this function)
> > > be-secure.c:621: warning: implicit declaration of function `S_ISREG'
> > > be-secure.c: In function `open_server_SSL':
> > > be-secure.c:704: `DEBUG' undeclared (first use in this function)
> > > gmake[3]: *** [be-secure.o] Error 1
> > > gmake[3]: Leaving directory `/home/chriskl/pgsql-head/src/backend/libpq'
> > > gmake[2]: *** [libpq-recursive] Error 2
> > > gmake[2]: Leaving directory `/home/chriskl/pgsql-head/src/backend'
> > > gmake[1]: *** [all] Error 2
> > > gmake[1]: Leaving directory `/home/chriskl/pgsql-head/src'
> > > gmake: *** [all] Error 2
> > >
> > > I will now recompile without debug symols or openssl perhaps...?
> > >
> > > Chris
> > >
> > > > -----Original Message-----
> > > > From: pgsql-hackers-owner@postgresql.org
> > > > [mailto:pgsql-hackers-owner@postgresql.org]On Behalf Of Bruce Momjian
> > > > Sent: Monday, 17 June 2002 3:04 PM
> > > > To: PostgreSQL-development
> > > > Subject: [HACKERS] Massive regression failures
> > > >
> > > >
> > > > I am seeing massive regression failures on a freshly
> > compiled, initdb'ed
> > > > version of CVS:
> > > >
> > > >  16 of 81 tests failed, 1 of these failures ignored.
> > > >
> > > > The first failure I see is:
> > > >
> > > >       COPY COPY_TBL FROM
> > > > '/usr/var/local/src/gen/pgsql/CURRENT/pgsql/src/test/regress/data/
> > > > constrf.data';
> > > >     - ERROR:  copy: line 2, CopyFrom: rejected due to CHECK
> > > > constraint copy_con
> > > >       SELECT * FROM COPY_TBL;
> > > >        x |       y       | z
> > > >     ! ---+---------------+---
> > > >     !  4 | !check failed | 5
> > > >     !  6 | OK            | 4
> > > >     ! (2 rows)
> > > >
> > > > Are others seeing this?  Cause?
> > > >
> > > > --
> > > >   Bruce Momjian                        |  http://candle.pha.pa.us
> > > >   pgman@candle.pha.pa.us               |  (610) 853-3000
> > > >   +  If your life is a hard drive,     |  830 Blythe Avenue
> > > >   +  Christ can be your backup.        |  Drexel Hill,
> > Pennsylvania 19026
> > > >
> > > > ---------------------------(end of
> > broadcast)---------------------------
> > > > TIP 3: if posting/reading through Usenet, please send an appropriate
> > > > subscribe-nomail command to majordomo@postgresql.org so that your
> > > > message can get through to the mailing list cleanly
> > > >
> > >
> > >
> >
> > --
> >   Bruce Momjian                        |  http://candle.pha.pa.us
> >   pgman@candle.pha.pa.us               |  (610) 853-3000
> >   +  If your life is a hard drive,     |  830 Blythe Avenue
> >   +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 5: Have you checked our extensive FAQ?
> >
> > http://www.postgresql.org/users-lounge/docs/faq.html
> >
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
> 

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


Re: Massive regression failures

От
"Christopher Kings-Lynne"
Дата:
Still badness on FreeBSD/Alpha:

gcc -pipe -O -g -Wall -Wmissing-prototypes -Wmissing-declarations -fpic -DPI
C -I. -I../../../src/include  -DFRONTEND -DSYSCONFDIR='"/home/chriskl/local/
etc/postgresql"'  -c -o fe-secure.o fe-secure.c -MMD
fe-secure.c: In function `verify_peer':
fe-secure.c:417: structure has no member named `s6_addr8'
gmake[3]: *** [fe-secure.o] Error 1
gmake[3]: Leaving directory `/home/chriskl/pgsql-head/src/interfaces/libpq'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory `/home/chriskl/pgsql-head/src/interfaces'
gmake[1]: *** [all] Error 2
gmake[1]: Leaving directory `/home/chriskl/pgsql-head/src'
gmake: *** [all] Error 2

Chris

> -----Original Message-----
> From: pgsql-hackers-owner@postgresql.org
> [mailto:pgsql-hackers-owner@postgresql.org]On Behalf Of Bruce Momjian
> Sent: Monday, 17 June 2002 11:11 PM
> To: Tom Lane
> Cc: PostgreSQL-development
> Subject: Re: [HACKERS] Massive regression failures
>
>
> Tom Lane wrote:
> > Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > > I am seeing massive regression failures on a freshly
> compiled, initdb'ed
> > > version of CVS:
> >
> > That's because you broke the regression test data files.
>
> Wow, I had a corrupted CVS regression directory.  I was seeing it during
> CVS update failure for the /regression directory, but I ignored it.
> Then I thought I saw a commit touching regression, which didn't make
> sense, but I closed the window too soon without investigating.
>
> Later, I deleted the directory and recreated it, but seems I had already
> accidentally modified those files.  I don't see any other /regression
> changes except /data, so I backed out those changes.  We should be OK
> now.
>
> > Kindly unbreak them ASAP.  I had wanted to do a cvs update this
> morning...
>
> Fixed now.
>
> --
>   Bruce Momjian                        |  http://candle.pha.pa.us
>   pgman@candle.pha.pa.us               |  (610) 853-3000
>   +  If your life is a hard drive,     |  830 Blythe Avenue
>   +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>