> There is a hook "post_parse_analyze_hook" but I think it comes too
> late as it comes after the analyze step which is when Postgres looks
> up the schema information for every relation mentioned in the query.
> What you would need is a post_parse_hook which would work on the raw
> parse tree befo
2014.02.15. dátummal, 0:46 időpontban Greg Stark írta:
> On Fri, Feb 14, 2014 at 9:16 PM, David Beck wrote:
>> Another point I liked in mysql is the possibility to write info schema
>> plugins:
>> http://dev.mysql.com/doc/refman/5.1/en/writing-information-schema-plugins.h
plugins:
http://dev.mysql.com/doc/refman/5.1/en/writing-information-schema-plugins.html
Like a virtual catalog. Is there anything similar in Postgres?
Thank you, David
2014.02.14. dátummal, 18:06 időpontban Greg Stark írta:
> On Fri, Feb 14, 2014 at 2:28 PM, David Beck wrote:
>> Why
?
Thanks, David
2014.02.14. dátummal, 10:30 időpontban David Beck írta:
> Thanks for the reply. There are two things I think I’ve been misunderstood:
>
> 1, the point is to do the rewrite without and before catalog access
> 2, I do want to push the join to the source and equal
időpontban Tom Lane írta:
> David Beck writes:
>> I have table like data structures in the source system for the FDW I work on.
>> These tables are sometimes too big and the source system is able to filter
>> and join them with limitations, thus it is not optimal to tra
o see why you wants the pseudo table "fdw_tableA_tableB" to
> be in the catalog,
> instead of the "tableA" and "tableB". In addition, parser shall raise
> an error if referenced
> columns (as a part of "tableA" or "tableB") are not in-cat
Hello Hackers,
I work on a foreign data wrapper for a legacy system. I generally find the hook
system very useful and flexible way to extend Postgres.
The post parse analyze hook almost fits what I need, but I have a few use cases
where I would need to tap right into the parsed queries but befor
