| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(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 05:40:21 |
| Message-ID: | 200001160540.AAA08665@candle.pha.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.)
Thanks. I missed that.
--
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2000-01-16 05:40:49 | Re: [HACKERS] I think we need an explicit parsetree node for CAST |
| Previous Message | Bruce Momjian | 2000-01-16 05:39:53 | Re: [HACKERS] I think we need an explicit parsetree node for CAST |