Re: [HACKERS] Re: pg_dump tries to do too much per query

2000-09-19 Thread Philip Warner
At 12:13 19/09/00 -0400, Tom Lane wrote: > >Say what? (... tries it ...) Fascinating. I wouldn't rely on this >behavior however; the fact that it works today is a totally unintended >consequence of a change I made for column alias support. Next week >ruleutils.c might try to access the underly

RE: [HACKERS] Re: pg_dump tries to do too much per query

2000-09-19 Thread Matthew
---Original Message- From: Tom Lane [SMTP:[EMAIL PROTECTED]] Sent: Tuesday, September 19, 2000 11:13 AM To: Philip Warner Cc: [EMAIL PROTECTED] Subject:Re: [HACKERS] Re: pg_dump tries to do too much per query I can't agree with

Re: [HACKERS] Re: pg_dump tries to do too much per query

2000-09-19 Thread Tom Lane
Philip Warner <[EMAIL PROTECTED]> writes: >>> 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

Re: [HACKERS] Re: pg_dump tries to do too much per query

2000-09-18 Thread Philip Warner
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

Re: [HACKERS] Re: pg_dump tries to do too much per query

2000-09-18 Thread Philip Warner
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

Re: [HACKERS] Re: pg_dump tries to do too much per query

2000-09-18 Thread Philip Warner
At 11:37 18/09/00 -0400, Tom Lane wrote: >Philip Warner <[EMAIL PROTECTED]> 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 solu

Re: [HACKERS] Re: pg_dump tries to do too much per query

2000-09-18 Thread Tom Lane
Philip Warner <[EMAIL PROTECTED]> 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 hac

[HACKERS] Re: pg_dump tries to do too much per query

2000-09-18 Thread Philip Warner
At 16:29 17/09/00 -0400, Tom Lane wrote: > >create table test (f1 int); >create view v_test as select f1+1 as f11 from test; >drop table test; > >then run pg_dump: > >getTables(): SELECT failed. Explanation from backend: 'ERROR: cache lookup of attribute 1 in relation 400384 failed >'. > FWIW,