Seg fault in initdb

I just tried to run initdb with the latest CVS snapshot but initdb
segfaults, i.e. some programs inside do:

Vacuuming template1
Segmentation fault
Segmentation fault
Creating public pg_user view
Segmentation fault
Segmentation fault
Segmentation fault
Creating view pg_rules
Segmentation fault
Segmentation fault
Creating view pg_views
Segmentation fault
Segmentation fault
Creating view pg_tables
Segmentation fault
Segmentation fault
Creating view pg_indexes
Segmentation fault
Segmentation fault
Loading pg_description
Segmentation fault
Segmentation fault
Segmentation fault

Is this a known problem? Or do I have a local problem on my machine?

I got a in-progress patch in the tree a few days ago, but reversed it
out in a few minutes. You probably have a copy from then. cvs update
should fix it.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@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

On Thu, Jul 22, 1999 at 03:18:29PM -0400, Bruce Momjian wrote:

I just tried to run initdb with the latest CVS snapshot but initdb
segfaults, i.e. some programs inside do:
...

I got a in-progress patch in the tree a few days ago, but reversed it
out in a few minutes. You probably have a copy from then. cvs update
should fix it.

Yes, initdb works fine now.

Michael
--
Michael Meskes | Go SF 49ers!
Th.-Heuss-Str. 61, D-41812 Erkelenz | Go Rhein Fire!
Tel.: (+49) 2431/72651 | Use Debian GNU/Linux!
Email: Michael.Meskes@gmx.net | Use PostgreSQL!

Michael Meskes <meskes@postgreSQL.org> writes:

On Thu, Jul 22, 1999 at 03:18:29PM -0400, Bruce Momjian wrote:

I just tried to run initdb with the latest CVS snapshot but initdb
segfaults, i.e. some programs inside do:

I got a in-progress patch in the tree a few days ago, but reversed it
out in a few minutes. You probably have a copy from then. cvs update
should fix it.

Yes, initdb works fine now.

Department of blame where blame is due: it was my bug not Bruce's ...
I fixed it about 11pm EDT last night.

regards, tom lane