| From: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>, "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>, "Tatsuo Ishii" <t-ishii(at)sra(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: current is broken |
| Date: | 2000-09-15 04:16:43 |
| Message-ID: | 3.0.5.32.20000915141643.0284ecb0@mail.rhyme.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At 22:23 14/09/00 -0400, Tom Lane wrote:
>
>Oh, I finally see the problem: when you come to dump out the rules, you
>need to avoid dumping the rules that correspond to views because you're
>going to emit the CREATE VIEW commands separately.
>
>You don't really need a rulekind though. If it's an ON SELECT rule for
>a relation that you've determined to be a view, then the rule is a
>view rule. Otherwise, you print the rule.
>
It looks like some nice person has defined the 'pg_rules' view which does
not return rules used in views. I'll try using this since it removes
another layer of backend knowledge from pg_dump.
----------------------------------------------------------------
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-15 05:43:25 | New pg_dump committed... |
| Previous Message | Philip Warner | 2000-09-15 02:44:52 | RE: current is broken |