Re: pg_group_name_index corrupt?

From: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: The Hermit Hacker <scrappy(at)hub(dot)org>, Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_group_name_index corrupt?
Date: 2000-05-05 05:37:48
Message-ID: 39125E2C.1B4FE0D2@alumni.caltech.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Hiroshi did commit a change to doc/src/sgml/ref/postgres-ref.sgml for
> that just a few days ago, but I guess it didn't make it into the derived
> files that Thomas was preparing off-line. I believe there were several
> other small doco fixes while Thomas was on vacation --- I dunno if he
> plans to try to get those into the 7.0 derived docs or not.

I'll move a new copy of the html into users-lounge before release, and
will try poking at the hardcopy versions too (but I consider the
hardcopy fixes noncritical since we are so far past the "freeze"
point).

Depends on the actual release schedule as to whether they will get in
to the hardcopy; the pg_group stuff doesn't open a large can of worms,
but we might want a few days for it to settle out??

btw, I'm all for fixing pg_group (it is really nonoptional imho) and
the ODBC stuff is noncritical since loading the contrib/odbc/odbc.sql
is sufficient to get the functions or operators defined since the
support code is already in the backend.

- Thomas

--
Thomas Lockhart lockhart(at)alumni(dot)caltech(dot)edu
South Pasadena, California

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message The Hermit Hacker 2000-05-05 05:40:01 Re: pg_group_name_index corrupt?
Previous Message Bruce Momjian 2000-05-05 05:37:46 Re: pg_group_name_index corrupt?