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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: pg_dump tries to do too much per query
Date: 2000-09-18 15:37:41
Message-ID: 14574.969291461@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Philip Warner <pjw(at)rhyme(dot)com(dot)au> writes:
> FWIW, the patch below causes get_viewdef to produce:
> ERROR: pg_get_viewdef: cache lookup of attribute 1 in relation 19136
> failed for rule v_test
> when a table has been deleted.

Not much of a solution --- or do you propose to go through and hack up
every elog in every routine that could potentially be called during
pg_get_ruledef?

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

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message The Hermit Hacker 2000-09-18 15:41:06 Re: ascii to character conversion in postgres
Previous Message Tom Lane 2000-09-18 15:21:47 Re: ascii to character conversion in postgres