Re: Two proposed modifications to the PostgreSQL FDW - Mailing list pgsql-hackers

From Chris Travers
Subject Re: Two proposed modifications to the PostgreSQL FDW
Date
Msg-id CAN-RpxB_S5GUtBejhXYdT=hBg0W5GzvHNuJHAxFZ49nVqs-QLA@mail.gmail.com
Whole thread Raw
In response to Re: Two proposed modifications to the PostgreSQL FDW  (Chris Travers <chris.travers@adjust.com>)
List pgsql-hackers
For the record, here's the proof of concept code for the transaction manager which works off libpq connections.

It is not ready yet by any means.  But it is included for design discussion.  If the previous patch gets in instead, that's fine, but figure it is worth including here for discussion purposes.

Two things which are currently missing are a) an ability to specify in the log file where the cleanup routine is located for a background worker and b) a separation of backend responsibility for restarting cleanup efforts on server start.




--
Best Regards,
Chris Travers
Head of Database

Tel: +49 162 9037 210 | Skype: einhverfr | www.adjust.com 
Saarbrücker Straße 37a, 10405 Berlin



--
Best Regards,
Chris Travers
Head of Database

Tel: +49 162 9037 210 | Skype: einhverfr | www.adjust.com 
Saarbrücker Straße 37a, 10405 Berlin

Attachment

pgsql-hackers by date:

Previous
From: Andrew Gierth
Date:
Subject: Re: A really subtle lexer bug
Next
From: Wu Ivy
Date:
Subject: Re: Getting NOT NULL constraint from pg_attribute