Re: Re: pg_dump tries to do too much per query - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: pg_dump tries to do too much per query
Date
Msg-id 14574.969291461@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_dump tries to do too much per query  (Philip Warner <pjw@rhyme.com.au>)
Responses Re: Re: pg_dump tries to do too much per query
Re: Re: pg_dump tries to do too much per query
List pgsql-hackers
Philip Warner <pjw@rhyme.com.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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: ascii to character conversion in postgres
Next
From: The Hermit Hacker
Date:
Subject: Re: ascii to character conversion in postgres