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

From Philip Warner
Subject Re: Re: pg_dump tries to do too much per query
Date
Msg-id 3.0.5.32.20000919104516.0286ac60@mail.rhyme.com.au
Whole thread Raw
In response to Re: Re: pg_dump tries to do too much per query  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
At 11:37 18/09/00 -0400, Tom Lane wrote:
>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?

Well, I had assumed that most routines/subsystems would identify themselves
as sources of errors, and that the behaviour of pg_get_viewdef was unusual.
Even the existing code for get_viewdef tries to output it's name in most
places, just not all.


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


pgsql-hackers by date:

Previous
From: Alex Sokoloff
Date:
Subject: Re: ascii to character conversion in postgres
Next
From: Philip Warner
Date:
Subject: Re: Re: pg_dump tries to do too much per query