> -----Original Message-----
> From: Jean-Michel POURE [mailto:jmpoure@axitrad.com]
> Sent: 20 September 2001 16:00
> To: pgadmin-hackers@postgresql.org
> Subject: Re: [pgadmin-hackers] Packages, Repository and Rebuilding
>
>
>
> >Functions don't have indexes.
> Sorry, it is the converse, I meant create an index on
> function (column). Let's take the example of a view: it can
> incorporate multiple functions, in
> case the view OID itself does not suffice.
> Do I miss something?
Simple, create all indexes last of all. The optimizer will figure out what
indexes to use (and cache the results) on a per query basis at runtime (if I
understand it correctly), hence you can add an index at any time and it will
be used where appropriate. The functions don't care about indexes at
creation time.
Like I, this is how I understand PostgreSQL does it. I may well be wrong.
> >No, basically it will dump the schema as an sql script from the
> >selected server or database. Alternatively, it will publish (==copy)
> >the schema to another specified database(s). Basically a
> mechanism for
> >moving your schema from a dev or staging server to one or more
> >production servers.
> This is what I need, good.
Thought you'd like it!
Dave.