From: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Re: pg_dump tries to do too much per query |
Date: | 2000-09-19 00:42:12 |
Message-ID: | 3.0.5.32.20000919104212.02862980@mail.rhyme.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
----------------------------------------------------------------
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 |/
From | Date | Subject | |
---|---|---|---|
Next Message | Philip Warner | 2000-09-19 00:45:16 | Re: Re: pg_dump tries to do too much per query |
Previous Message | Alex Sokoloff | 2000-09-18 22:25:48 | Re: ascii to character conversion in postgres |