Re: FDW API / flow charts for the docs? - Mailing list pgsql-hackers

From Fabrízio de Royes Mello
Subject Re: FDW API / flow charts for the docs?
Date
Msg-id CAFcNs+pmTG0qWcAO_rFb1KazkcL5heuk7HxL98pBnRP3G=E4_Q@mail.gmail.com
Whole thread Raw
In response to FDW API / flow charts for the docs?  (Tomas Vondra <tv@fuzzy.cz>)
List pgsql-hackers
<div dir="ltr"><div class="gmail_extra">On Wed, Oct 16, 2013 at 8:35 PM, Tomas Vondra <<a
href="mailto:tv@fuzzy.cz">tv@fuzzy.cz</a>>wrote:<br />><br />> [...]<br />><br />> Attached is the set
offlow charts, showing the sequence of callbacks<br /> > for all the supported commands (i.e. SELECT, INSERT,
UPDATE,DELETE,<br />> ANALYZE).<br /><br /></div><div class="gmail_extra">Thank you very much... this flow charts
willhelp many people, including me ;-)<br /></div><div class="gmail_extra">  <br /><br />> Wouldn't it be useful to
putsomething like this into the<br />> docs? I mean, the FDW API is not going to get any simpler, and for me<br
/>>this was a significant help.<br />><br /><br /></div><div class="gmail_extra"> +1 to add into docs.<br
/></div><divclass="gmail_extra"><br /></div><div class="gmail_extra">I think we can add this flow charts to [1].<br
/></div><divclass="gmail_extra"><br />Regards,<br /><br />[1] <a
href="http://www.postgresql.org/docs/9.3/interactive/fdwhandler.html">http://www.postgresql.org/docs/9.3/interactive/fdwhandler.html</a><br
/><br/>--<br />Fabrízio de Royes Mello<br />Consultoria/Coaching PostgreSQL<br />>> Timbira: <a
href="http://www.timbira.com.br">http://www.timbira.com.br</a><br/>>> Blog sobre TI: <a
href="http://fabriziomello.blogspot.com">http://fabriziomello.blogspot.com</a><br/> >> Perfil Linkedin: <a
href="http://br.linkedin.com/in/fabriziomello">http://br.linkedin.com/in/fabriziomello</a><br/>>> Twitter: <a
href="http://twitter.com/fabriziomello">http://twitter.com/fabriziomello</a></div></div>

pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: FDW API / flow charts for the docs?
Next
From: Robert Haas
Date:
Subject: Re: [PATCH] pg_sleep(interval)