<div>06.07.2015, 20:28, "Guillaume Lelarge" <guillaume@lelarge.info>:</div><div>> That sounds a lot like a
backgroundworker.</div><div>Thank a lot! That's exactly what I was looking for.</div><div> </div><div>07.07.2015,
03:29,"Jim Nasby" <Jim.Nasby@BlueTreble.com>:<br />> There is support for plugging into the parser and
executor,so that<br />> might be a possibility, but...</div><div>For now, it's the key question as I didn't find
anythinglike that in PostreSQL docs. There are some good samples of implementing custom background workers but all them
useprepared stetements via SPI.</div><div> </div><div>> AFAIK HTSQL is very happy producing SQL; why not just let it
handSQL to <br />> Postgres (which it already does...)</div><div>Yes, they both work like a charm but HTSQL is
implementedin Python which adds some extra overhead.<br /><br />> Have you by chance talked to Clark or Kirill about
this?<br/>Not yet. I'm not currently going to follow all the HTSQL specs (at least at the starting point), just will
usethem as reference.</div>