Re: Re: pg_dump tries to do too much per query

At 10:42 19/09/00 +1000, Philip Warner wrote:
>At 11:37 18/09/00 -0400, Tom Lane wrote:
>>
>>The reason that changing pg_dump is a superior solution for this problem
>>is that there's only one place to change, not umpteen dozen ...
>>
>
>Well at least two, unless you like the following:
>
> zzz=# select * from pg_views;
> ERROR: cache lookup of attribute 1 in relation 3450464 failed
>

Apologies - I just noticed you fixed this in CVS, so it now manages
(somehow!) to output a valid view definition even without the underlying
table. A little scary, though.

----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/