From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)atentus(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_dump and inherited attributes |
Date: | 2002-09-25 04:01:24 |
Message-ID: | 27371.1032926484@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Alvaro Herrera <alvherre(at)atentus(dot)com> writes:
> I'm looking at pg_dump/common.c:flagInhAttrs() and suspect that it can
> be more or less rewritten completely, and probably should to get rigth
> all the cases mentioned in the past attisinherited discussion. Is this
> desirable for 7.3? It can probably be hacked around and the rewrite
> kept for 7.4, but I think it will be much simpler after the rewrite.
If it's a bug then it's fair game to fix in 7.3. But keep in mind that
pg_dump has to behave at least somewhat sanely when called against older
servers ... will your rewrite behave reasonably if the server does not
offer attinhcount values?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-09-25 04:49:34 | Re: making use of large TLB pages |
Previous Message | Tom Lane | 2002-09-25 03:57:29 | Re: contrib/earthdistance missing regression test files |
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2002-09-25 09:38:32 | Re: DROP COLUMN misbehaviour with multiple inheritance |
Previous Message | Alvaro Herrera | 2002-09-25 00:45:14 | Re: DROP COLUMN misbehaviour with multiple inheritance |