Greetings,
I was thinking about an old 2007 topic, where schema
qualification was proposed on the EXPLAIN output
(http://archives.postgresql.org/pgsql-
hackers/2007-06/msg00473.php).
Besides my need for this "feature" for my own PgFoundry
project (that need to parse the explain output), at th
Greetings,
I was thinking about an old 2007 topic, where schema
qualification was proposed on the EXPLAIN output
(http://archives.postgresql.org/pgsql-
hackers/2007-06/msg00473.php).
Besides my need for this "feature" for my own PgFoundry
project (that need to parse the explain output), at th
2007/9/17, Tom Lane <[EMAIL PROTECTED]>:
>
> "Cristiano Duarte" <[EMAIL PROTECTED]> writes:
> > Is there a way to have access to PostgreSQL query plan and/or predicates
> > inside a function using spi (or any other way)?
>
> No.
>
> Hi Tom,
he function call?
Is the query plan saved in memory at a place where a spi function can have
access?
Regards,
Cristiano Duarte.
Alvaro Herrera wrote:
> Cristiano Duarte wrote:
>
>> SQL table aliases doesn't help locating the real place where the table
>> is. If I have a table named "test" at the schema "place" and I do:
>>
>> "EXPLAIN SELECT * FROM place.tes
Gurjeet Singh wrote:
> I don't think Cristiano is asking for the schema_name in the
> EXPLAIN o/p.
In fact I'm requesting for schema_name in EXPLAIN o/p.
> The request is for the table ALIASes to be shown in the
> o/p, which makes more sense than schema_name+table_name, since the
> same ta
log table (wich is placed on the same schema as
the master table).
Any help would be greatly appreciated.
Regards,
Cristiano Duarte
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index sc
