Re: [HACKERS] INDEX_MAX_KEYS and pg_dump

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

>> 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.

It was broken --- I committed fixes for it at about 11PM EST.

(The same problem as for func args --- it wasn't coping with
zero suppression in oidvectorout/int2vectorout.)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2000-01-16 05:36:21 Re: [HACKERS] pg_dump not in very good shape
Previous Message Tom Lane 2000-01-16 04:22:42 Re: [HACKERS] I think we need an explicit parsetree node for CAST