Re: TODO updates

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: TODO updates
Date: 2000-07-24 03:27:59
Message-ID: 15131.964409279@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>> Philip Warner <pjw(at)rhyme(dot)com(dot)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?

Oh, I see, you're emitting the underlying table and the rule separately.
Yeah, I think that will probably work.

Is it safe to postpone ACL setting? Less sure about that ... I think
the rule parser checks ACLs at parse time instead of execution, for
example.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Philip Warner 2000-07-24 03:35:13 Re: TODO updates
Previous Message Philip Warner 2000-07-24 00:50:07 Re: TODO updates