nill writes:
> I am analyzing query plans generated by the view in the database PostgreSQL
> 8.3, looking for missing information "constraints not explicitly registrants
> in the tables."
You realize of course that 8.3 is nearly 7 years old and has been out of
support for awhile.
> In the analys
I am analyzing query plans generated by the view in the database PostgreSQL
8.3, looking for missing information "constraints not explicitly registrants
in the tables."
In nested queries, (ex. IN clause, ...), the query plan consist in the
evaluation of the subplane derived from clause (SELECT * ..
There seem to be several ways to get at just about anything in the
Catalog Tables. The ODBC driver, psql, and pg_dump typically use
slightly diff sql and you guys have suggested even better ways. Forgive
me as I ask for more.
How do I determine the foriegn keys in a table?
I see pg_class.relfkey
Hannu Krosing <[EMAIL PROTECTED]> writes:
> Peter Harvey wrote:
>> 2. How do I determine the AccessMethod specified when an index was
>> created?
> you can parse it from pg_indexes.indexdef
... which relies on pg_get_indexdef(index OID).
Or, look at pg_class.relam, which is zero for regular ta
Peter Harvey wrote:
>
> Great progress today on my Reverse Engineering efforts. However; I have
> some comments.
>
> 1. How can I switch databases (where I would normally use USE)?
You just open another connection .
If you mean psql jou do
\c otherdatabasename
> 2. How do I determine the Acc
Great progress today on my Reverse Engineering efforts. However; I have
some comments.
1. How can I switch databases (where I would normally use USE)?
2. How do I determine the AccessMethod specified when an index was
created?
3. It would be cool if the catalog objects had comments on them in
p
