Re: [HACKERS] INDEX_MAX_KEYS and pg_dump

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Mike Mascari <mascarm(at)mascari(dot)com>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] INDEX_MAX_KEYS and pg_dump
Date: 2000-01-16 04:05:30
Message-ID: 200001160405.XAA28804@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Hello,
>
> I grabbed last nights snapshot to come up with a diff for
> pg_dump to generate COMMENT ON statements for user-defined
> descriptions. However, I believe pg_dump is currently in a
> broken state with respect to the dumping of indexes,
> possibly related to the current work done with
> INDEX_MAX_KEYS. Can anyone confirm this?

I just looked and I don't see any problems.

--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Don Baccus 2000-01-16 04:07:30 Re: [HACKERS] I think we need an explicit parsetree node for CAST
Previous Message Bruce Momjian 2000-01-16 02:41:09 Re: [HACKERS] I think we need an explicit parsetree node for CAST