Re: TODO updates - Mailing list pgsql-hackers

From Philip Warner
Subject Re: TODO updates
Date
Msg-id 3.0.5.32.20000724105007.0262f500@mail.rhyme.com.au
Whole thread Raw
In response to Re: TODO updates  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: TODO updates  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
At 12:36 23/07/00 -0400, Tom Lane wrote:
>Philip Warner <pjw@rhyme.com.au> writes:
>> As of the latest pg_dump, it dumps in modified oid order: rules, triggers,
>> views and indexes always go at end, but the rest is in oid order.
>
>Hmm, I think you need to dump views in OID order just as though they
>were tables.  What if an SQL function refers to a view?

The actual list of things it moves to the end is: TABLE DATA, BLOBS, INDEX,
TRIGGER, RULE and ACL. The underlying table for a view is created in OID
order, so I would guess that referencing it in an SQL function would still
be OK. Is that OK?




----------------------------------------------------------------
Philip Warner                    |     __---_____
Albatross Consulting Pty. Ltd.   |----/       -  \
(A.C.N. 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: Thomas Lockhart
Date:
Subject: Re: State of RPMs
Next
From: Tom Lane
Date:
Subject: Re: TODO updates